[DOCS-108] Tutorial: dump/restore method of bulk-deleting data Created: 12/Jan/12 Updated: 30/Oct/23 Resolved: 15/Jan/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Kristina Chodorow (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 11 years, 5 weeks, 1 day ago |
| Comments |
| Comment by auto [ 15/Jan/13 ] |
|
Author: {u'date': u'2013-01-15T14:59:38Z', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: |
| Comment by Scott Hernandez (Inactive) [ 15/Jan/13 ] |
|
We should add a note somewhere that if deleting a lot of the collection then it might be better to just save the ones you want in a new collection. You can either use dump/restore or just write a script to create the new collection+index and swap, but because of indexes it is a much better solution many times than TTL collections, just like dynamic collections based on date ranges are, for example. |
| Comment by Sam Kleinman (Inactive) [ 15/Jan/13 ] |
|
TTL collections are the right answer for this kind of problem. |