[DOCS-1163] Clarify paddingFactor on compact Created: 26/Feb/13 Updated: 06/Mar/13 Resolved: 06/Mar/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | James Wahlin | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 10 years, 50 weeks ago | ||||
| Description |
|
When a padding factor is included as part of our collection compact command, this factor is used to add padding to existing records during compaction. It does not impact future inserts in which padding is driven from statistics gathered to date. This behavior is not clear in our main description. We have included a note on this in the "Note the following behaviors" section but this is easy to miss. Please update to make this more visible. The above is in reference to the following page: |
| Comments |
| Comment by auto [ 06/Mar/13 ] |
|
Author: {u'date': u'2013-03-01T02:27:16Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by auto [ 06/Mar/13 ] |
|
Author: {u'date': u'2013-03-01T02:27:16Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |