Ziyue Hua created TINKERPOP-2778:
Summary: Wrong result in executing queries
Key: TINKERPOP-2778
URL: https://issues.apache.org/jira/browse/TINKERPOP-2778
Project: TinkerPop
Issue Type: Bug
Divij, that is a good point, and I supposed eliminates the need for special
async interfaces at the structure API level. W.r.t. a deep push-based
rethinking of Gremlin query evaluation, I think it is worth thinking about,
but it does sound TP4-y. If I can hearken all the way back to Ripple, each
I see. I guess I didn't get how those steps should be rewriten yet. In case
graph providers provide an event loop to TinkerPop then I think it could be
done like that. I thought your idea was to have that event loop in
TinkerPop itself. That said, maybe we shouldn't even bother working with an
Just to clarify, I am not thinking about a client/server architecture.
I am talking only about TinkerPop's core step implementation.
So I think just a library like Reactor (no netty) is needed for that
part.
Regards
Pieter
On Sat, 2022-07-30 at 12:43 +0100, Oleksandr Porunov wrote:
> I used
I used Vert.x before, and know that framework uses an even loop to solve
that issue. I believe Reactor Netty also uses event loop to solve the issue
with infinite callback chains.
I.e. instead of having a callback which calls another callback which calls
another callback and so on till
