Some more progresss on Cascading

Is that already in the cascading branch? As far as I can tell it's still a single input (the join command specifies the same ancestor twice), which is fine. Cascading supports that in theory, but I run into something I believe is a bug, hence the comment. I recreated it with a pure java version.