[
https://issues.apache.org/jira/browse/TINKERPOP-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP-1439.
---------------------------------------
Resolution: Won't Do
Side-effects aren't really used.In retrospect we probably shouldn't have
bothered with them in the first place. Don't want to do this anymore as it
would just further promote their existence.
> Determine what to do if specific host is unavailable
> ----------------------------------------------------
>
> Key: TINKERPOP-1439
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1439
> Project: TinkerPop
> Issue Type: Improvement
> Components: driver
> Affects Versions: 3.2.2
> Reporter: stephen mallette
> Priority: Major
>
> When the user submits a request with the "host" parameter it tells the driver
> to route the request to the value specified in that host. This feature is
> typically used internally by a remote traversal where the user wants to
> retrieve a side-effect (as the side-effect lives on the host the traversal
> was original executed on). Of course, if the host is unavailable for some
> reason when the user tries to retrieve their side-effect, the driver will
> result with an error.
> Need to consider how to best handle this - perhaps the traversal could be
> re-submitted to a different host and iterated behind the scenes and thus
> allow the user to get their side-effect without knowing anything went bad?
> See {{Client.chooseConnection()}} implementation for where this logic
> currently lives.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
