You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our goal is to order everything based on the fieldToOrderOn but only if the filterValueToMatch matches our inputted value, every other fieldToOrderOn value should be ignored.
Expected Result
Given filterValueToMatch 1234 with descending ordering we expect:
Item1 (orderValue 2 for 1234)
Item2 (orderValue 1 for 1234)
Actual result:
Item2 (orderValue 1 for 1234, but with orderValue 3 for 4567)
Item1 (orderValue 2 for 1234)
Any help would be appreciated :)
The text was updated successfully, but these errors were encountered:
NEST/Elasticsearch.Net version:
NEST: 7.17.5
Elasticsearch version:
8.12.2
.NET runtime version:
8.0.2
Operating system version:
n/a, happens both local and on all of our cloud deployments
Description of the problem including expected versus actual behavior:
Nested ordering seems to ignore the filter when ordering the results.
Our indexed objects look something like this;
Our sort descriptor looks something like this:
Our goal is to order everything based on the
fieldToOrderOn
but only if thefilterValueToMatch
matches our inputted value, every otherfieldToOrderOn
value should be ignored.Expected Result
Given filterValueToMatch
1234
with descending ordering we expect:2
for1234
)1
for1234
)Actual result:
1
for1234
, but with orderValue3
for4567
)2
for1234
)Any help would be appreciated :)
The text was updated successfully, but these errors were encountered: