UNSHARDED version should have a valid timestamp

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: 5.1 Required
    • Component/s: Sharding
    • None
    • v5.1
    • Sharding EMEA 2021-10-04, Sharding EMEA 2021-10-18
    • 46
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Right now we we define the timestamp of UNSHARDED as Timestamp(0, 0) but it looks like this value has a special semantic: when it is used on a CRUD op it means to get the current time.

      From our side we can change it to Timestamp(0, 1) or something like that.

            Assignee:
            Sergi Mateo Bellido
            Reporter:
            Sergi Mateo Bellido
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: