honestly really didn't consider it much. Still think it was the right move.
-
-
Replying to @posco @avibryant
not disputing the choice, just face with a similar one and was looking for deep insights
1 reply 0 retweets 1 like -
I've almost never regretted composition over inheritance.
3 replies 1 retweet 8 likes -
you are soon going to hear from
@THISWILLWORK about FileSource1 reply 0 retweets 3 likes -
Replying to @krishnansriram @bigdatasc and
I have certainly regretted cases of inheritance over composition. Source is #1.
2 replies 0 retweets 3 likes -
Replying to @posco @krishnansriram and
I am working on a proposal for a new FileSource, the main theme is composition
1 reply 0 retweets 3 likes -
Replying to @THISWILLWORK @posco and
I've been wondering if a new Source abstraction should always return Execution[TypedPipe[T]]
2 replies 0 retweets 0 likes -
Replying to @avibryant @THISWILLWORK and
the reasoning there is, roughly, that a Source is just a materialized job.
1 reply 0 retweets 0 likes -
Replying to @avibryant @THISWILLWORK and
it's not clear that a downstream user should know/care about the "materialized" part.
1 reply 0 retweets 0 likes -
Replying to @avibryant
the apis get fun fast. Path presence testing, toIterator =/= toIterableExecution, planner implications of push down map to src
1 reply 0 retweets 0 likes
yeah, definitely needs to be a lower level API for things like toIterator. But the default happy path should go through Execution.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.