-
Notifications
You must be signed in to change notification settings - Fork 765
SOLR-17319 : Combined Query Feature for Multi Query Execution #3418
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 1 commit
bf3cd5d
182bec9
b884f0e
29e8aea
c113799
3600ed3
9b0c76e
a841bc7
91f8e09
cace1f7
299db43
840070e
d2feefc
89f63a9
d821abb
8041d66
397dbb3
d8b5588
ec0b9cb
d6fd190
86933bc
b164979
85f2cf9
a4a26aa
7fe997c
bcd1c3b
787a016
7e0727c
4dcbb57
8a65023
006b8c2
771089b
460e8cd
ac85d2f
7b0593c
c03c0f7
a52dd22
195f3f1
c1f5501
3649d3e
4eedbed
0990e7f
14ff5e1
bd637b7
2958599
c3e44c3
e2dfcef
d4b34fc
3fe93b8
f23cceb
6419a07
a560899
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please update this test to not call In order for this test to compare both single shard & multi-shard with score relevancy, you could do a couple different things. One is to use the ExactStatsCache for distributed-IDF. Or, write queries that set a constant/fixed score. That would actually be most clear. With such a test, you don't need to test non-distributed since the test infrastructure here allows you to do both as one. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. True, but I also wanted to show the results are not the same as what was expected in a single shard, as I described in the jira issue. Asserting only ideal queries (like constant/fixed score) or a type of queries (lexical with ExactStatsCache) may not give a clear picture to the algorithm IMHO. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I concur that in a realistic setting, sharding will yield score variances or ties that could change the final ordering. But why test under that circumstance? It only makes testing harder and for a reader of the tests to understand that the assertions are valid. We won't have less test coverage by fixing the scores somehow. I think the vast majority of tests here should operate in this circumstance, which makes them clear to understand / validate. This should save you time (less tests to maintain). If the way RRF tie brakes matters (I doubt it), I could understand adding such a test to ensure we don't introduce a regression. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Alright, I have removed the Non-distributed test case separately using |
Uh oh!
There was an error while loading. Please reload this page.