[SERVER-48434] Rename LogicalTimeMetadataHook to VectorClockMetadataHook Created: 27/May/20  Updated: 29/Oct/23  Resolved: 30/Dec/20

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

Type: Improvement Priority: Minor - P4
Reporter: Kevin Pulo Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Participants:

 Description   

The move of cluster time from LogicalClock to VectorClock on SERVER-47914 means that the LogicalTimeMetadataHook egress class is now less about hooking for the purpose of "logical time", and more about doing it for the vector clock, hence it should be renamed to VectorClockMetadataHook.



 Comments   
Comment by Ian Whalen (Inactive) [ 04/Jan/21 ]

Author:

{'username': u'evrg-bot-webhook', 'name': u'Pierlauro Sciarelli', 'email': u'pierlauro.sciarelli@mongodb.com'}

Message:SERVER-48434 Rename LogicalTimeMetadataHook to VectorClockMetadataHook
Branch:master
https://github.com/mongodb/mongo/commit/0921aed12a0c1be5abc63190670a3e2dcf84c610

Comment by Pierlauro Sciarelli [ 31/Dec/20 ]

Link to commit. (Commenting manually due to broken Github-Jira hook)

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