[SERVER-50514] Custom default indexes per DB Created: 25/Aug/20 Updated: 27/Aug/20 Resolved: 27/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor - P4 |
| Reporter: | Wojciech Waga | Assignee: | Eric Sedor |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Some projects (like mine) use collections to separate some data realms. Users are free to create a new realm via API and we in turn create a new collection (one per realm). The problem we have is that we need to have a separate component that creates a set of indices used by our app as the API itself does not know them. It would be handy if one could specify a set of indices for all newly created collections within a DB (instead of just the index on _id). |
| Comments |
| Comment by Eric Sedor [ 27/Aug/20 ] |
|
We are tracking support for this feature in SERVER-3573. Can you please watch that ticket for updates and/or post information about your need and use-case there? Gratefully, |