[SERVER-20582] _id time reflects end of chunk instead of beginning Created: 23/Sep/15 Updated: 27/Oct/15 Resolved: 22/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bruce Lucas (Inactive) | Assignee: | Mark Benvenuto |
| Resolution: | Done | Votes: | 0 |
| Labels: | FTDC | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Platform A (10/09/15), Platform B (10/30/15) | ||||
| Participants: | |||||
| Description |
|
The _id field of the chunk documents is a datetime at or later than the last of the samples in the chunk. The spec says it should be the "clock immediately before the record was first collected", and this is a reasonable definition, consistent with the timestamp used for the filename indicating the beginning of the samples in the file. A stable definition for these timestamps is helpful for efficient filtering of a date range when processing the files. |
| Comments |
| Comment by Githook User [ 22/Oct/15 ] |
|
Author: {u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}Message: |