-
Type:
Sub-task
-
Resolution: Fixed
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Integration
-
Fully Compatible
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Several helper functions currently determine whether or not an extension-implemented $vectorSearch exists in the pipeline. The following table explains which of these functions will be generalized to also check for extension-implemented $search/$searchMeta and which use a separate helper function.
| Function | Generalize or Separate | Reasoning |
| search_helper_bson_obj::isExtensionVectorSearchPipeline() | Generalize to isExtensionMongotPipeline() | Used without $vectorSearch-specific logic. |
| search_helpers:isExtensionVectorSearchPipeline() | Generalize to isExtensionMongotPipeline() | Used without $vectorSearch-specific logic. |
| search_helpers::isExtensionVectorSearchStage() | Separate | Used guarding a $vectorSearch-specific counter. |
| DocumentSourceExtensionOptimizable::LiteParsedExpand\\{able\\|ed}::hasExtensionVectorSearchStage()\ | Separate | Used guarding a $vectorSearch-specific counter. |
| LiteParsedPipeline::hasExtensionVectorSearchStage() | Separate | Used guarding a $vectorSearch-specific counter. |
Appropriate unit testing for these helpers should be included in this ticket as well.
- depends on
-
-
- Closed
-
- is depended on by
-
-
- Backlog
-
-
-
- Closed
-