There are a number of issues related to the UI timing out or providing unhelpful feedback after a long-running query: #114 #181 #168 #108. We currently have the /query request HTTP handler processing the query which is expected to regularly take multiple minutes up to half an hour. The UI in unable to tell what is happening until the request returns or fails. I think there might be several advantages to moving to a queue service:
the queue could report to the user a more fine-grained current status of the query
the queue could warn the user if the generated neo4j query is inefficient
allows the frontend to let the user queue up multiple queries instead of opening a new browser tab
allows the user to cancel the request
Would be curious to hear thoughts on this, but maybe there are other solutions that get us some of the benefits without introducing a new service.
hina-shah
commented
1 month ago
There are a number of issues related to the UI timing out or providing unhelpful feedback after a long-running query: #114 #181 #168 #108. We currently have the /query request HTTP handler processing the query which is expected to regularly take multiple minutes up to half an hour. The UI in unable to tell what is happening until the request returns or fails. I think there might be several advantages to moving to a queue service:
Would be curious to hear thoughts on this, but maybe there are other solutions that get us some of the benefits without introducing a new service.