-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add queuing feature to all bulk import methods #704
Comments
@paynejd This should be available now |
My baseline bulk import for PEPFAR country mappings took ~185sec with the old import method. The bulk import method took just 75seconds! I did not see queue key anywhere on the bulk import UI, but it used to be there -- was that field hidden? That would be useful to control the queue key still so that we could manage the order in which bulk import files are processed. For example, I may want to submit 10 bulk imports to the same queue key - this would force the files to be processed in the order in which they were submitted. The queue key would be a useful field to display in the list of existing imports as well. Next step for testing is to make sure that the scripts can get all the info that they need about queued imports, as this is how they determine if an import is in process. |
@paynejd Enabled custom-queue field for every user. |
@paynejd The queue key is displayed in existing imports as well. |
Initial testing went great - closing this out! Additional testing will take place as part of #613 |
The bulk import queue feature was added to the original
/manage/bulkimport
endpoint, but it is not yet available in the inline/parallel versions. We want this feature to be available in all of the bulk import endpoints.After this is completed, we can continue work on #613
The text was updated successfully, but these errors were encountered: