[SERVER-28146] Add version field to signature of LogicalTimeMetadata Created: 28/Feb/17  Updated: 06/Dec/22  Resolved: 08/May/17

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

Type: New Feature Priority: Major - P3
Reporter: Randolph Tan Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Sprint: Sharding 2017-03-27, Sharding 2017-04-17
Participants:

 Description   

This is for possible format changes, like upgrading SHA1 to SHA256.

Existing format:

logicalTime: {
    clusterTime: <Timestamp>,
    signature: <SHA1 hash of clusterTime as BinData>
}

New format:

logicalTime: {
    clusterTime: <Timestamp>,
    signature: { version: <int>, hash: <SHA1 hash of clusterTime as BinData> }
}



 Comments   
Comment by Randolph Tan [ 28/Feb/17 ]

Sounds good to me

Comment by Andy Schwerin [ 28/Feb/17 ]

Could we put the version into the timeproof instead of the LTM? That is, if we're mostly interested in handling different signature algorithms, why not put the version information into the signature instead?

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