QA: review Ming update, mongo commands in the comment above, and the attached python script. I've tested each with a unit test or manually, so a code review is probably sufficient.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Still need to add new version of ming to requirements-common.txt
After trying the new update_indexes on the Allura models, I saw it drop indexes and not recreate them on children of polymorphic inheritance (ForumAttachment) But they were auto-created later, not sure what's going on entirely.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
description has changed
Need to convert app_config_id_1_ticket_num_1 index from regular to unique. Would be good if Ming's update_indexes handled changing the unique flag.
Ming update http://merciless.git.sourceforge.net/git/gitweb.cgi?p=merciless/merciless;a=commitdiff;h=7f9c9383bdbff042b44fc379ed91ed6db6d0fc9b
I used this query in each of project-data-* to find other duplicates. Found one more.
To fix the duplicates, run:
Then with a new version of ming, run the ensure index command
And also run the attached script to update solr.
QA: review Ming update, mongo commands in the comment above, and the attached python script. I've tested each with a unit test or manually, so a code review is probably sufficient.
gtg
Created https://control.sog.geek.net/sog/trac/ticket/18050 encapsulating all the commands
Still need to add new version of ming to requirements-common.txt
After trying the new update_indexes on the Allura models, I saw it drop indexes and not recreate them on children of polymorphic inheritance (ForumAttachment) But they were auto-created later, not sure what's going on entirely.
With [#1482] fixing the index updating logic, just waiting for https://control.sog.geek.net/sog/trac/ticket/18050 now
Related
Tickets:
#148218050 is done, but the tickets have reduplicated