-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Rework RRF to be evaluated during rewrite phase #112648
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
Changes from 79 commits
57ec072
5e5839e
73f4f8f
115ea36
3bff589
191307a
78b193b
3e0574a
b33fa45
2c6c2c6
32ccffd
8cebaf7
7d0a7a1
7490ac9
87449fc
1222284
6d23639
e03c48e
e6387ab
18a9c74
ab40ea5
0179298
26f89b6
20f4047
ff78c5e
db9b469
9388c02
a7935af
5d5fe89
d26053e
8decb0a
ebdd321
598345e
b4a182c
57214b8
24c4c6e
2c9a597
27ae7cb
8866345
5e08637
5179aa5
06ec538
5d42f41
ce1c55f
d08161a
9e1a747
bfb6181
c2c63fe
4f7b775
a63dd95
123f996
bf15a0e
456b1bc
db98014
986babe
d2752e9
b331dc6
620290f
b5fb4cf
fd540aa
520df49
77c19ba
b90dff8
ceecfaf
57860c0
9dcdfed
555bb4c
4c20964
89d67d6
dd415f2
fd83384
d5478d6
4e7eb4e
2366d4c
2c19f2a
1a9ccdd
b623bee
9fdc501
ff05d13
ec9c725
885c4b2
af5ae62
6b1fd8a
beeab5d
96d2973
9d1532d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -502,6 +502,8 @@ void executeRequest( | |
}); | ||
final SearchSourceBuilder source = original.source(); | ||
if (shouldOpenPIT(source)) { | ||
// disabling shard reordering for request | ||
original.setPreFilterShardSize(Integer.MAX_VALUE); | ||
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. We might want to document (in a later PR) and call this out as a known limitation. Indicating that we do not skip serializing to nodes with zero valid results. Clarifying that we won't actually gather any results. It would also be good to know if this will cause us to fetch metadata in frozen. Serializing to the node and then doing an actual no-op, is ok. But if we actually skip the cluster state information and fetch timestamp metadata, that would be bad. 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.
Why is that? The min/max timestamp for frozen indices is cached. It's not ideal that we have to skip the can match on the coordinating node but it won't cause any additional I/Os on the frozen tier, just additional back and forth. |
||
openPIT(client, original, searchService.getDefaultKeepAliveInMillis(), listener.delegateFailureAndWrap((delegate, resp) -> { | ||
// We set the keep alive to -1 to indicate that we don't need the pit id in the response. | ||
// This is needed since we delete the pit prior to sending the response so the id doesn't exist anymore. | ||
|
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rank
has now been removed so we just rely onscore
anddoc