[SERVER-34100] Make the Chunk object not expose implementation details of the ChunkManager Created: 23/Mar/18  Updated: 29/Oct/23  Resolved: 23/Apr/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.7.6

Type: Task Priority: Major - P3
Reporter: Martin Neupauer Assignee: Martin Neupauer
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-04-09, Sharding 2018-04-23, Sharding 2018-05-07
Participants:

 Description   

Having a getShardIdAt method on the chunk (which is provided by the
ChunkManager) exposes the internal implementation of the ChunkManager. If you
get a ChunkManager with timestamp 100, you shouldn't be allowed to ask for where
that chunk was at timestamp 50, because this is a potential for programmer
error.

That's why I want the Chunk that you get from the CM to come with the same
Timestamp as the CM.

If doing Misha's suggestion unblocks integration with GPiTR I am fine with
checking it in, but we need to have a ticket to disallow that.



 Comments   
Comment by Githook User [ 23/Apr/18 ]

Author:

{'email': 'martin.neupauer@10gen.com', 'username': 'MartinNeupauer', 'name': 'Martin Neupauer'}

Message: SERVER-34100 - Make the Chunk object not expose implementation details of the ChunkManager
Branch: master
https://github.com/mongodb/mongo/commit/559910472384b3625fca4d9eca47dd9d165c6958

Generated at Thu Feb 08 04:35:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.