Based on:
https://lists.apache.org/thread.html/de4ec9054fd7a88cbd42163a0b105019aae52a7e930b09a9bd4c971d@%3Cdev.tinkerpop.apache.org%3E
We have a pretty serious bug that I can't seem to find a workaround for.
The only workaround I can think of would be to replace this:
Lambda.function("it.get()")
with
new OneArgLambda("it.get()", "gremlin-groovy")
Not great as existing code using Lambda will break and none of the docs
make any reference to direct usage of the various "Lambda" constructors.
So, short of someone suggesting one very quickly, I think we need to
release a patch.
Any concerns with doing that? Also, assuming we proceed with the patch as
quickly as possible, can anyone think of any critical items that need to be
done for 3.2.9/3.3.3?
As a side note, this is somewhat good for gremlin-javascript as we sorta
flubbed the documentation a bit and missed some odds/ends.....perhaps this
allows us to get that patched up as well sooner than expected?
