You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tinkerpop.apache.org by "Lyndon Bauto (Jira)" <ji...@apache.org> on 2024/05/29 20:23:00 UTC

[jira] [Created] (TINKERPOP-3081) When using authentication, evaluationTimeout is ignored

Lyndon Bauto created TINKERPOP-3081:
---------------------------------------

             Summary: When using authentication, evaluationTimeout is ignored
                 Key: TINKERPOP-3081
                 URL: https://issues.apache.org/jira/browse/TINKERPOP-3081
             Project: TinkerPop
          Issue Type: Bug
            Reporter: Lyndon Bauto
            Assignee: Lyndon Bauto


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 

{{final long seto = args.containsKey(Tokens.ARGS_EVAL_TIMEOUT) ?
                ((Number) args.get(Tokens.ARGS_EVAL_TIMEOUT)).longValue() : context.getSettings().getEvaluationTimeout();}} 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) 
!https://media.discordapp.net/attachments/1245462911728615629/1245462912085000325/image.png?ex=6658d739&is=665785b9&hm=42ae08309e9f54cc8c0db61ed131d3b7efb92dfbd0f82fc7c3b2ee20e4cf7be9&=&format=webp&quality=lossless&width=550&height=340!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)