[SERVER-12302] Breaking Change: Timestamp(0,0) now replaced on insert Created: 09/Jan/14 Updated: 14/Jan/14 Resolved: 09/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.4.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Shaun Verch | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
This causes things like the Timestamp not round tripping correctly doing a dump restore from 2.4 to 2.5 (this bug does not exist in 2.5) |
| Comments |
| Comment by Shaun Verch [ 09/Jan/14 ] |
|
The way I found this issue was by doing dump/restore testing from 2.4 to 2.5. In 2.5 we replace the Timestamp even if it is not the first field. |
| Comment by Scott Hernandez (Inactive) [ 09/Jan/14 ] |
|
This is by design; is there some use-case or test this is failing because of this? On insert we now fill in all TimeStamp(0,0) with a server generated one. Before we only did so if the field was the 1st/2nd (including _id which is first) one. |