You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Stephen Mallette (Jira)" <ji...@apache.org> on 2020/09/14 20:00:00 UTC

[jira] [Updated] (TINKERPOP-2210) Support cancellation of remote traversals

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

Stephen Mallette updated TINKERPOP-2210:
----------------------------------------
    Component/s:     (was: dotnet)
                 server
    Description: 
It should be possible to cancel a remote traversals in Gremlin, for example when an application shuts down. This involves the following steps:
 * Cancel the send operation.
 * Cancel the task the user is awaiting on by cancelling the underlying {{TaskCompletionSource}}. This means that any received data for this traversal needs to be ignored afterwards.
 * Cancel the operation on the server if possible.

I'm not sure if / how we can cancel the operation on the server. If it's not easy to do that right now, then we should just start by cancelling everything only client-side.

  was:
It should be possible to cancel a traversal in Gremlin.Net, for example when an application shuts down. This involves the following steps:
 * Cancel the send operation.
 * Cancel the task the user is awaiting on by cancelling the underlying {{TaskCompletionSource}}. This means that any received data for this traversal needs to be ignored afterwards.
 * Cancel the operation on the server if possible.

I'm not sure if / how we can cancel the operation on the server. If it's not easy to do that right now, then we should just start by cancelling everything only client-side.

        Summary: Support cancellation of remote traversals  (was: Support cancellation of traversals in Gremlin.Net)

This was originally written with .NET in mind but I've generalized it to a "server" issue instead.

> Support cancellation of remote traversals
> -----------------------------------------
>
>                 Key: TINKERPOP-2210
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2210
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.4.1
>            Reporter: Florian Hockmann
>            Priority: Minor
>
> It should be possible to cancel a remote traversals in Gremlin, for example when an application shuts down. This involves the following steps:
>  * Cancel the send operation.
>  * Cancel the task the user is awaiting on by cancelling the underlying {{TaskCompletionSource}}. This means that any received data for this traversal needs to be ignored afterwards.
>  * Cancel the operation on the server if possible.
> I'm not sure if / how we can cancel the operation on the server. If it's not easy to do that right now, then we should just start by cancelling everything only client-side.



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