Hi Jeff, thanks for your inquiry. There has not been much more discussion
on this issue that I can recall, though recently improvements are being
made into cancelling sessions which would effectively cancel a long run
query:
https://issues.apache.org/jira/browse/TINKERPOP-2336
I'm not yet sure
My team is experimenting with JanusGraph and in that context we ran into some
situations where it would be handy to have exactly the kind of functionality
that is proposed here. Has there been any more discussion since these emails
(I realize this exchange is from over a year ago)?
If not, is
Yes, scoping this to bytecode is a good idea. Is there any risks in trying
to support this for HTTP requests? (Supporting sessions and scripts may
easily bloat up the scope. so your concern there is very valid).
Either way, what would be the next steps to take this forward?
Karthik
On Wed, Nov
I like the thought for explicit cancellation, but I think that before we
get into what that would look like or how it would work, we'd need to
determine the scope of what we wanted to allow cancellation of. We have
scripts (both with and without a session) and we have bytecode based
requests. I
Hi Team,
This is a followup of a SO discussion[1] with Stephen where I wanted to see
if we can add language constructs for 1) Listing running queries 2)
Cancelling a running query. Something straightforward would look like this:
g.query() or g.Q() -> Iterator for all running queries
