[
https://issues.apache.org/jira/browse/TINKERPOP-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP-2213:
----------------------------------------
Labels: breaking (was: deprecation)
Description: {{scriptEvaluationTimeout}} doesn't fit well with bytecode
based requests because they aren't actually "scripts" - consider just
{{evaluationTimeout}}? (was: {{scriptEvaluationTimeout}} doesn't fit well with
bytecode based requests because they aren't actually "scripts" - consider
deprecating for something else, perhaps just {{evaluationTimeout}}?)
Summary: Replace scriptEvaluationTimeout in favor of something more
suitable to bytecode (was: Deprecate scriptEvaluationTimeout in favor of
something more suitable to bytecode)
Deprecation doesn't look easy to do because the setting is configured by way of
a public field in {{Settings}}....i can't think of a way to have a change in
one trigger replication to the other. I'm thinking we just look to remove the
old configuration in 3.5.0 and just have this be a breaking change.
> Replace scriptEvaluationTimeout in favor of something more suitable to
> bytecode
> -------------------------------------------------------------------------------
>
> Key: TINKERPOP-2213
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2213
> Project: TinkerPop
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.3.6
> Reporter: stephen mallette
> Assignee: stephen mallette
> Priority: Major
> Labels: breaking
>
> {{scriptEvaluationTimeout}} doesn't fit well with bytecode based requests
> because they aren't actually "scripts" - consider just {{evaluationTimeout}}?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
