You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the HTTP API, there is the option to add "x-arango-async: store" to the headers so that a query can be run asynchronously, in the sense that a job id is returned and results can be fetched later. Is this option also possible through the Java API? I understand that the API already has Java futures, but I would not like my app to have many background threads waiting for results on queries. Would it be possible to have the API return just a future of a job id, which the client can reference at a later time to fetch the results?
The text was updated successfully, but these errors were encountered:
I understand your point of view. This sounds like a valid use case but we don't have a good implementation story for this kind of feature at this time.
In the HTTP API, there is the option to add "x-arango-async: store" to the headers so that a query can be run asynchronously, in the sense that a job id is returned and results can be fetched later. Is this option also possible through the Java API? I understand that the API already has Java futures, but I would not like my app to have many background threads waiting for results on queries. Would it be possible to have the API return just a future of a job id, which the client can reference at a later time to fetch the results?
The text was updated successfully, but these errors were encountered: