Deprecate support for sharding time-series collections on time field

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • None
    • 3
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      Allowing time-series collections to be sharded on the time field adds complexity and special handling for time-series in code.

      Because a time-series bucket contains a range of time and may overlap it is impossible without certain restrictions (such as fixed bucketing) to determine which shard owns a particular time.

      It makes building features such as unique indexes for time-series collections more difficult and inefficient.

      Users with large time-series workloads typically have (very) high cardinality and sharding on meta is sufficient.

      By deprecating support for sharding time-series collections on the time field, we can remove it in the future to allow for simplifications of the code.

              Assignee:
              Unassigned
              Reporter:
              Henrik Edin
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: