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

Time-series bucket change stream `shardCollection` events translate shardKey fields

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.0-rc0, 7.0.2, 7.1.0-rc2
    • Affects Version/s: None
    • Component/s: None
    • None
    • Sharding EMEA
    • Fully Compatible
    • ALL
    • v7.1, v7.0
    • Sharding EMEA 2023-08-21, Sharding EMEA 2023-09-04, Sharding EMEA 2023-09-18

      Problem

      Against v7 and latest I see this in a `shardCollection` event:

      {operationDescription [{shardKey [{mytimefield 1}]} {unique false} {numInitialChunks 0} {presplitHashedZones false} {timeseries [{timeField mytimefield} {metaField mymetafield} {granularity seconds} {bucketMaxSpanSeconds 3600}]} {collation [{locale simple}]}]}
      

      Note the translated, “logical” field name.

      Against v6, though, I see `control.min.mytimefield` and `meta` as the shardKey field names. Apparently that’s correct, per arun.banala@mongodb.com.

      Solution & Acceptance Criteria

      v6, v7, and latest should all behave as expected.

      Impact

      This will impact REP-35. I’m going to try to work around it for now by recognizing logical field names & converting them to the bucket field names.

            Assignee:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Reporter:
            felipe.gasper@mongodb.com Felipe Gasper
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: