Uploaded image for project: 'MongoDB Shell'
  1. MongoDB Shell
  2. MONGOSH-1747

Mongosh should correctly parse timeseries options without the presence of `unique` field.

    • Type: Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Priority: Icon: Major - P3 Major - P3
    • No version
    • Affects Version/s: None
    • Component/s: None
    • None
    • Environment:
      OS:
      node.js / npm versions:
      Additional info:
    • Not Needed
    • Developer Tools

      Problem Statement/Rationale

      If I follow the instructions here to create an empty sharded timeseries collection on latest master locally:
      https://www.mongodb.com/docs/manual/core/timeseries/timeseries-shard-collection/

      i.e

      sh.shardCollection(   "test.weather",   { "metadata.sensorId": 1 },   {      timeseries: {         timeField: "timestamp",         metaField: "metadata",         granularity: "hours"      }   }) 

      I actually don't see the timeseriesFields being set on the doc for the collection in the config.collections collection i.e it's not creating a timeseries collection.

      Please be sure to attach relevant logs with any sensitive data redacted.
      How to retrieve logs for: Compass; Shell

      Steps to Reproduce

      How could an engineer replicate the issue you’re reporting?

      Expected Results

      Mongosh should correctly parse timeseries options without the presence of `unique` field.

      Actual Results

      What do you observe is happening?

      Additional Notes

      Any additional information that may be useful to include.

            Assignee:
            Unassigned Unassigned
            Reporter:
            kshitij.gupta@mongodb.com Kshitij Gupta
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: