Theo
When lots of futures are given to `Future.after` you can get a stack overflow error since each callback registers as a callback to the next future, and the call stack...
It's really annoying that the relation names in the code that Piglet produces are all relation_1, relation_2 and so on. There should be a way to set the name of...
It's unlikely that Piglet will cover every single aspect of Pig Latin, so it would be good to have a way of injecting Pig Latin code verbatim.
Pig has a whole bunch of file commands that Piglet does not support.
a.join(b => :x, a => :y) is non-deterministic since the order of key keys in the hash is not guaranteed. sometimes it will come out as "JOIN a BY y,...
This is currently not supported by Piglet: FOREACH p GENERATE a + 3, b + 1, c + 5 AS (x:int, y:int, z:int)
In Piglet, this is currently not possible: FOREACH x GENERATE A.(b, c) i.e. dereference both A.b and A.c at the same time, I think it's equivalent to A.b, A.c.
This is currently not possible in Piglet: FOREACH x GENERATE * where the star means "all fields"
It would be nice if you could choose to use "generate" instead of "foreach" as the name of the foreach…generate operation in Piglet, i.e. a.foreach { |r| … } could...
This removes the dependency on the MessagePack Java libraries in favour of a rewritten encoder and decoder that was made especially for JRuby. The non-standard extensions that were in msgpack-jruby...