Hi Steve,
Sorry, we are pretty busy with the release of v 3.0.0, I'll try to follow
up as soon as I can.
The traverse() executor is still there, but only in the old SQL executor.
The new parser (strict SQL) was implemented for the new executor, so it
doesn't make much sense to have it in the
Luigi,
I haven't heard back on this.
Since the backend to the traverse() is still there, we're wondering how
much trouble it would be to add it into the new parser.
It definitely has some powerful and unique use cases. If these aren't
covered by the new match projection, I would suggest that
