Potential bug in evaluationTimeout when using auth?
When i use g.with("evaluationTimeout", X).call(<some call step).next() without authentication it works. When I do it with authentication enabled it does not work.
The offending code appears to be this piece of TraversalOpProcessor.java
Which returns properly without authentication enabled as args contains "evaluationTimeout", but when authentication is enabled, that key does not exist, and instead it is embedded deeper down (see attached pic, it's in configuration of the OptionsStrategy deep down)
Has anyone seen this issue before?
The offending code appears to be this piece of TraversalOpProcessor.java
Which returns properly without authentication enabled as args contains "evaluationTimeout", but when authentication is enabled, that key does not exist, and instead it is embedded deeper down (see attached pic, it's in configuration of the OptionsStrategy deep down)
Has anyone seen this issue before?
Apache TinkerPop is an open source graph computing framework and the home of the Gremlin graph query language.
1,376Members
Resources
Similar Threads
Was this page helpful?
