@posco @peterseibel you know what would be cool? For typed Scalding jobs, graphviz output of the "type flow" from inputs to outputs.
-
-
Replying to @avibryant
@avibryant@posco@peterseibel +100. would help beginners learning scalding so much, and would help understand complicated flows.1 reply 0 retweets 0 likes -
Replying to @daashu
@daashu@posco@peterseibel any thoughts about implementation? Seems like type erasure makes this painful. Cache all the manifests?1 reply 0 retweets 0 likes -
Replying to @avibryant
@avibryant@daashu@peterseibel compiler plugin or macro. The latter probably.1 reply 0 retweets 0 likes -
Replying to @posco
@posco@avibryant@daashu@peterseibel Yeah it would be quite easy to write a graph { ... } macro if the job was literally defined inside.2 replies 0 retweets 0 likes -
Replying to @d6
@d6@avibryant@daashu@peterseibel I think that is a find constraint for this kind of debug out.1 reply 0 retweets 0 likes -
Replying to @posco
@posco@d6@daashu@peterseibel hm, really? Means it wouldn't work when your job used, say, the DISCO stuff, or other similar libraries.2 replies 0 retweets 0 likes
@posco @d6 @daashu @peterseibel ... I feel like we could get a lot out of storing the Manifest chain in FlatMapFn, + equivalent in Grouped
-
-
Replying to @avibryant
@avibryant@d6@daashu@peterseibel as@0x138 reminds me: Manifests are invariant, which will complicate the variance of this.0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.