[SERVER-27723] Remove or un-deprecate ChunkType::DEPRECATED_epoch and ChunkType::DEPRECATED_lastmod Created: 17/Jan/17 Updated: 06/Dec/17 Resolved: 23/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.10 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Joanna Huang |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2017-07-10 |
| Participants: |
| Description |
|
It looks like these two fields were labeled deprecated when they were first written in this commit. It doesn't look like ChunkType::DEPRECATED_epoch is used meaningfully anywhere: it exists in unit tests, and we write it for commit split/merge chunk operations. I don't think ChunkType::DEPRECATED_lastmod is going to be removed anytime soon, since it's the ChunkVersion field of a chunk. |
| Comments |
| Comment by Githook User [ 23/Jun/17 ] |
|
Author: {u'name': u'Joanna Huang', u'email': u'joannahuang@Joannas-MacBook-Pro.local'}Message: |
| Comment by Dianna Hohensee (Inactive) [ 01/Jun/17 ] |
|
Update: ChunkType::DEPRECATED_epoch seems to be used now. Just get rid of the deprecated part. |