Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 9.0.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- ext-optimizations-m3

Assigned Teams:

Query Integration
Backwards Compatibility:
Fully Compatible
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Add PipelineRewriteContext::getPipelineBounds() and expose get_pipeline_bounds() in the extensions API so logical agg stages can derive min/max docs from pipeline suffix for batch size tuning and limit parity. Add appropriate unit and integration tests.

depends on

SERVER-122007 Refactor DocsNeededBounds interface

Closed

fixes

SERVER-89546 Refactor search libraries so extractDocsNeededBounds can be referenced in search helper code

Backlog

is related to

SERVER-118423 Implement DocsNeededBounds for extensions API

In Code Review

related to

SERVER-126930 Complete TODO listed in SERVER-122005

Needs Scheduling

Assignee:: Adithi Raghavan
Reporter:: Adithi Raghavan
Participants:: Adithi Raghavan, Githook User
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Mar 18 2026 05:30:16 PM UTC
Updated:: May 16 2026 04:13:50 AM UTC
Resolved:: May 07 2026 02:18:57 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates