Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-48434

Rename LogicalTimeMetadataHook to VectorClockMetadataHook

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Minor - P4 Minor - P4
    • 4.9.0
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible

      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.

            Assignee:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Reporter:
            kevin.pulo@mongodb.com Kevin Pulo
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: