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

extend min/max pushdown for $group for fixed bucketing

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • Fully Compatible
    • QI 2023-07-10, QI 2023-07-24, QI 2023-08-07, QI 2023-08-21

      This ticket will handle implementing the validation that will check if the $group for min/max optimization can occur. The requirements for this optimization are...

      1. bucketMaxSpanSeconds and bucketRoundingSeconds parameters have not been changed.
      2. Given a predicate on timeField T, dateTrunc(T) matches the bucket boundaries. For example, if bucketMaxSpanSeconds is set to 60 seconds, then dateTrunc.unit converted to seconds multiplied by dateTrunc.binSize needs to be a multiple of bucketMaxSpanSeconds.
      3. The $group _id field only refers to a combination of the metaField and dateTrunc(timeField).
      4. The query does not use an extended range.

      This ticket should also check that special timezones such as UTC +05:30 are gracefully handled.

            Assignee:
            gil.alon@mongodb.com Gil Alon
            Reporter:
            gil.alon@mongodb.com Gil Alon
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: