[SERVER-43059] Make read and write versions for KeyString Created: 27/Aug/19  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Xiangyu Yao (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-43178 Don't append the end byte to KeyStrin... Backlog
Assigned Teams:
Storage Execution
Participants:

 Description   

KeyStrings used for read(query) and write(index insertion) are quite different in its internal format: read KeyStrings always have discriminator at the end while write KeyStrings most of the time have RecordId in it. There is no easy way to quickly tell whether a KeyString is used for read or write. And people could misuse the encode/decode methods.

We should define better contracts or have different versions for KeyStrings.


Generated at Thu Feb 08 05:02:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.