-
Type:
Sub-task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
DB Integration & Observability
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Specify query-settings-rejection bypass, isSearchStage, and canRunOnTimeseries override values (true).
We currently do not allow extensions to provide these per-stage LP replacement values (ex: override LPDS::isSearchStage() = true) to avoid unexpected behavior that could stem from a extension stage wrongly declaring itself as a $search stage, for example.
But, the server could instead provide the policy with the desired overrides, something like this.
// host-side, server-owned. Populated only for a registered stage that is the native // counterpart of a built-in. Never sourced from extension input. struct NativeReplacementPolicy { bool bypassQuerySettingsRejection = false; // native $listSearchIndexes: true bool isSearchStage = false; // native $listSearchIndexes: true ;
For canRunOnTimeseries:
'canRunOnTimeseries' default-false property must be added to extension_agg_stage_static_properties.idl which $listSearchIndexes can override
- is depended on by
-
SERVER-138475 Add host-side first-demand target resolution for the extension $listSearchIndexes stage
-
- Backlog
-
- is related to
-
SERVER-129047 Expose stage-level properties on extension ParseNode for hybrid-search eligibility
-
- Closed
-