Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.2.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- M4
- dino-search

Assigned Teams:

DB Integration & Observability
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 combination.expression to ScoreFusionSpec (and remove the old "score" field on the spec) and implement corresponding behavior in document_source_score_fusion.

More info about combination.expression here.

Per design review discussions, should appropriately handle cases where pipeline name is used for a variable in combination.expression (ex: check whether variable is in scope).

Add a test to handle $let in the expression which can be used to duplicate a variable but the duplicated variable should follow natural scoping behavior and ultimately not cause confusion.

depends on

SERVER-100167 Implement "combination.method" behavior

Closed

is depended on by

SERVER-101079 Add $scoreFusion tests that assert document results on rentals dataset

Closed

SERVER-102534 Make ScoreFusionScoringOptions private

Closed

is duplicated by

SERVER-94624 Implement the 'score' argument for $scoreFusion

Closed

related to

SERVER-104736 Enable referencing collection level variables in $scoreFusion expression combination option without 'docs.' prefix

Closed

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

Created:: Jan 30 2025 03:41:33 PM UTC
Updated:: Oct 23 2026 06:45:38 PM UTC
Resolved:: Mar 20 2025 09:20:56 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates

PagerDuty