NICTA/scoobi — pull request #20 by espringe (2011-12-08 03:03:45+00:00)
Title: Handle an MSCR with a flatten, but no group-by-key

The part's I'm most unsure of:

plan/AST.scala: is the "mkDummyTaggedMapper" ok? It seems like the proper name would be "mkIdentityTaggedMapper" but that's already used by the MapperLike stuff, where it enforces that type is a Key-Value pair. I wonder if there's an opportunity for some code reuse?

plan/Intermediate.scala I broke the nice functional style, opting for a mutable set. This was because there was no longer a 1:1 inputChannel to outputChannel ratio. Is there a way I'm missing that would make this more readable?