[
https://issues.apache.org/jira/browse/TINKERPOP-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17611071#comment-17611071
]
ASF GitHub Bot commented on TINKERPOP-2794:
-------------------------------------------
FlorianHockmann opened a new pull request, #1818:
URL: https://github.com/apache/tinkerpop/pull/1818
https://issues.apache.org/jira/browse/TINKERPOP-2794
This enables users to cancel the evaluation of a single traversal / the
execution of a submitted script.
Cancellation on the server is however out of scope for this contribution as
we first need TINKERPOP-2210 for that. So this frees up resources on the client
and requests that were not successfully submitted to the server yet can also be
cancelled completely.
The first commit comes from #1817 which I used here already as this change
adds a lot of changes that are technically breaking changes and would therefore
require a lot of suppressions for compatibility warnings.
VOTE +1
> Allow cancellation of Gremlin.Net async methods
> -----------------------------------------------
>
> Key: TINKERPOP-2794
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2794
> Project: TinkerPop
> Issue Type: Improvement
> Components: dotnet
> Reporter: Bill Poole
> Assignee: Florian Hockmann
> Priority: Major
>
> Gremlin.Net async methods such as Promise do not accept a CancellationToken
> parameter and cannot therefore be cancelled. Applications often need to be
> closed quickly/responsively when a user quits or an application server
> component is shut down/rebooted - e.g., during cluster auto
> scaling/rebalancing.
> All async methods should accept a CancellationToken parameter (which can be
> given a default value of 'default').
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
