[jira] [Updated] (TINKERPOP-2438) Provide a way for scripts to respect with() specification of timeout

["Stephen Mallette (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TINKERPOP-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephen Mallette updated TINKERPOP-2438:
----------------------------------------
    Fix Version/s:     (was: 3.4.9)
                       (was: 3.5.0)

> Provide a way for scripts to respect with() specification of timeout
> --------------------------------------------------------------------
>
>                 Key: TINKERPOP-2438
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2438
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.4.8
>            Reporter: Stephen Mallette
>            Assignee: Stephen Mallette
>            Priority: Major
>
> This issue sorta relates to the Gremlin Console but I think it's generally a server side problem as it could easily occur with HTTP or just scripts sent over web sockets. Folks tend to see all the ways they can set timeouts and then mix/match them. It only remains a problem with sending a script as {{g.with("evalTimeout",100)}} because the server won't know that this value was set until the script is passed to {{eval()}} but by then it's too late because we would have already started the timeout countdown.  While most users wouldn't send that as a bare script submission it's a common mistake in the Gremlin Console and similar environments where it is not clear you are working with a remote graph. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)