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
Right now the search API prioritized realtime response and returns in 2-5 seconds. Can we build support for long time consuming search operations by doing them via the queue?
So basically when a client makes an API request for search, the request gets queued up in rabbit mq. Then when a consumer is available, it gets the job and performs the long search operation and then notifies the client via an API. We could later on explore alternate ways of reporting back like email, slack etc
The text was updated successfully, but these errors were encountered:
Right now the search API prioritized realtime response and returns in 2-5 seconds. Can we build support for long time consuming search operations by doing them via the queue?
So basically when a client makes an API request for search, the request gets queued up in rabbit mq. Then when a consumer is available, it gets the job and performs the long search operation and then notifies the client via an API. We could later on explore alternate ways of reporting back like email, slack etc
The text was updated successfully, but these errors were encountered: