Story #152
closed
As a user, I can add custom indexes to mongo collections
Status:
CLOSED - CURRENTRELEASE
Description
Some users want the ability to search on a particular field of a particular collection frequently, and thus need the ability to define custom indexes. Right now, pulp will destroy user-defined indexes when pulp-manage-db runs.
Deliverables:
- move the drop and create indexes code from pulp-manage-db into a new migration
- add a release note that only after running pulp-manage-db one last time will the user's indexes are now safe to be added and they will not be dropped
- add a note in the user facing docs that users are free to add/manage their own migrations on mongodb
- add a section to the developer docs that explains a migration needs to be used for deletion of indexes in the future
- the new migration needs to come with tests
Once we switch fully to mongoengine, we can get rid of the dumb thing
that drops the index with each pulp-manage-db.
Once we've done that, my preference would be for us to stop dropping the
indices in pulp-manage-db, and leave it to the user to use the Mongo
shell to add their own custom indices.
- Tags Sprint Candidate added
Some users want the ability to search on a particular field of a particular collection frequently, and thus need the ability to define custom indexes. Right now, pulp will destroy user-defined indexes when pulp-manage-db runs.
Deliverables:
- move the drop and create indexes code from pulp-manage-db into a new migration
- add a release note that only after running pulp-manage-db one last time will the user's indexes are now safe to be added and they will not be dropped
- add a note in the user facing docs that users are free to add/manage their own migrations on mongodb
- add a section to the developer docs that explains a migration needs to be used for deletion of indexes in the future
- Description updated (diff)
- Description updated (diff)
- Sprint/Milestone set to 12
- Status changed from NEW to ASSIGNED
- Assignee set to dkliban@redhat.com
- Status changed from ASSIGNED to POST
- Status changed from POST to MODIFIED
- Tags deleted (
Sprint Candidate)
- Platform Release set to 2.7.0
- Status changed from MODIFIED to 5
- Status changed from 5 to CLOSED - CURRENTRELEASE
- Sprint set to February 2015
- Sprint/Milestone deleted (
12)
Also available in: Atom
PDF