Timeseries filtering can miss extended-range events when sharded

XMLWordPrintableJSON

    • Query Integration
    • Fully Compatible
    • ALL
    • v8.0, v7.3, v7.0, v6.0, v5.0
    • Execution Team 2024-02-19, Execution Team 2024-03-04
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In SERVER-66469 we fixed timeseries filtering of extended-range data by disabling some predicate pushdown optimizations for collections that have the "requires extended range support" in-memory flag set.

      However, this flag is per-process, so any time one node plans a query to be executed on another, we need to know the value of the flag where the query will execute.

      SERVER-66469 attempts to fix this by checking the flag during view resolution, which in a sharded cluster happens on the primary shard. So if the collection contains extended-range data, but none of it is on the primary shard, mongos will push down more predicates than it should, and the query can miss events outside the 32-bit range.

      We need some mechanism for mongos to know whether extended-range events exist anywhere in the collection.

              Assignee:
              Chris Wolff
              Reporter:
              David Percy (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              24 Start watching this issue

                Created:
                Updated:
                Resolved: