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.
- is caused by
-
SERVER-62356 shardCollection for time-series is not done under the critical section
-
- Closed
-
- related to
-
SERVER-80943 Add a test to assert the change stream output format for time-series shardCollection operation
-
- In Code Review
-