In order timeseries measurements spanning epoch-time are incorrectly promoted to version 3

XMLWordPrintableJSON

    • Storage Execution
    • Fully Compatible
    • ALL
    • Hide

      This can be reproduced with a few shell commands 

      db.createCollection("ts", {timeseries: {timeField:"t", granularity: "seconds"}})
db.ts.insert({t: new Date("1969-12-31T23:59:58Z"), data: {a: "b"}}))
db.ts.insert({t: new Date("1970-01-01T00:00:01Z"), data: {x: "y"}}))

db.ts.validate() // returns valid == false, errors includes v3 in-order bucket
      Show
      This can be reproduced with a few shell commands  db.createCollection( "ts" , {timeseries: {timeField: "t" , granularity: "seconds" }}) db.ts.insert({t: new Date( "1969-12-31T23:59:58Z" ), data: {a: "b" }})) db.ts.insert({t: new Date( "1970-01-01T00:00:01Z" ), data: {x: "y" }})) db.ts.validate() // returns valid == false , errors includes v3 in-order bucket
    • Storage Execution 2026-04-13
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When inserting documents into a collection with pre-epoch timestamps, inserting documents into the same bucket that are post-epoch results in a version 3 bucket despite the collection meeting the criteria for version 2.

       

            Assignee:
            Benjamin Pearce
            Reporter:
            Benjamin Pearce
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: