Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.1.0-rc0, 8.0.4
Affects Version/s: 7.0.2, 6.0.11
Component/s: Aggregation Framework
Labels:

Assigned Teams:

Query Integration
Backwards Compatibility:
Fully Compatible
Backport Requested:

v8.0, v7.0
Sprint:
QI 2024-06-24, QI 2024-07-08, QI 2024-07-22, QI 2024-08-05, QI 2024-08-19, QI 2024-09-02, QI 2024-09-16, QI 2024-09-30
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

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

This is the preferred method for hybridizing limited result sets from search pipelines, as indicated in this tutorial and referenced in the PD for ordered/scored result set fusion.

We should provide a mechanism for this so that users can hybridize vector with vector or lexical with vector without being concerned about ordering of pipelines.

is depended on by

SERVER-88602 Support $vectorSearch in lookup subpipeline

Open

is related to

SERVER-104016 Remove enableUnionWithVectorSearch query knob

Closed

Assignee:: Reilly McBride (Inactive)
Reporter:: Henry Weller
Participants:: Githook User, Henry Weller, Reilly McBride
Votes:: 0 Vote for this issue
Watchers:: 10 Start watching this issue

Created:: Mar 15 2024 02:50:26 PM UTC
Updated:: Apr 18 2025 03:43:15 PM UTC
Resolved:: Sep 24 2024 03:18:27 PM UTC
Confidence Status Last Update:: 18/Jun/24 4:44 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates