[
https://issues.apache.org/jira/browse/TINKERPOP-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Mallette closed TINKERPOP-2517.
---------------------------------------
Fix Version/s: 3.5.0
Assignee: Stephen Mallette
Resolution: Done
> Introduce a retry status code to the server protocol
> ----------------------------------------------------
>
> Key: TINKERPOP-2517
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2517
> Project: TinkerPop
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.4.10
> Reporter: Stephen Mallette
> Assignee: Stephen Mallette
> Priority: Major
> Fix For: 3.5.0
>
>
> There is no common server code that defines when applications should retry a
> request. Without such a code, developers are left to (1) write provider
> specific code (i.e. Neptune retry codes vs JanusServer codes) and/or (2)
> parse response error messages to determine if retry is needed. If TinkerPop
> specified a code or code series that signified retry users could easily
> depend on it in their application logic. We would not look to implement retry
> logic in the drivers themselves - that would remain a task for application
> developers. Looking at the current response codes I'd think that we would
> just add {{SERVER_ERROR_TEMPORARY 596}}
> cc/ [~divijvaidya]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
