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
As we currently do with chunks using the -c option, we could introduce a -q option to specify a different queue for the import process.
This would help address issues when handling high-volume live data with the library. When we modify our Searchable model, we need to re-import the entire database. With over 100 million documents to process, we don’t want new live data saved by users to be delayed in the queue until all import jobs are completed.
A simple solution would be to use separate queues: one for live data saved by users and another for import jobs.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
As we currently do with chunks using the -c option, we could introduce a -q option to specify a different queue for the import process.
This would help address issues when handling high-volume live data with the library. When we modify our Searchable model, we need to re-import the entire database. With over 100 million documents to process, we don’t want new live data saved by users to be delayed in the queue until all import jobs are completed.
A simple solution would be to use separate queues: one for live data saved by users and another for import jobs.
Beta Was this translation helpful? Give feedback.
All reactions