[SERVER-1502] Generate indexes on a permanent map/reduce collection before it's swapped Created: 28/Jul/10 Updated: 12/Jul/16 Resolved: 09/Nov/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.7.3 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Thijs Cadier | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 5 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
It would be great if it was possible to define indexes on an output collection of a map/reduce before the permanent output collection was swapped. This would be very useful for scenario's where an application uses map/reduced data that's re-generated periodically to for example display pre-calculated data to users. There are use cases where you want to select data in a huge map/reduced output and need indexes to make this perform well. I could supply our use case if that's interesting to you. If the collection would be swapped by the periodical updater after an index is generated performance would not be degraded by indexing because the index would already be in place. |
| Comments |
| Comment by auto [ 10/Nov/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: fix slave indexes |
| Comment by auto [ 09/Nov/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: copy indexes from permanent mr output collections before renaming so no hiccup |
| Comment by auto [ 02/Nov/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: some thoughts on getting things from indexes |