-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
rework search api to allow searching on multiple caches at once #26874
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
icewind1991
force-pushed
the
single-query-search
branch
6 times, most recently
from
May 10, 2021 12:55
0f50fe1
to
0d97f7e
Compare
icewind1991
force-pushed
the
single-query-search
branch
6 times, most recently
from
May 26, 2021 15:58
7cf651e
to
acf974c
Compare
icewind1991
changed the title
[wip] rework search api to allow searching on multiple caches at once
rework search api to allow searching on multiple caches at once
May 26, 2021
icewind1991
added
3. to review
Waiting for reviews
and removed
2. developing
Work in progress
labels
May 26, 2021
blizzz
reviewed
Jun 2, 2021
blizzz
reviewed
Jun 2, 2021
blizzz
reviewed
Jun 2, 2021
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.
Just skimmed, did not see anything that is very obvious off.
Please check the code scanning findings, they seem reasonable.
skjnldsv
approved these changes
Jun 2, 2021
skjnldsv
added
4. to release
Ready to be released and/or waiting for tests to finish
3. to review
Waiting for reviews
and removed
4. to release
Ready to be released and/or waiting for tests to finish
labels
Jun 2, 2021
icewind1991
force-pushed
the
single-query-search
branch
from
June 10, 2021 12:31
acf974c
to
097fc68
Compare
rebase fixed ci :) |
Signed-off-by: Robin Appelman <robin@icewind.nl>
Signed-off-by: Robin Appelman <robin@icewind.nl>
Signed-off-by: Robin Appelman <robin@icewind.nl>
Signed-off-by: Robin Appelman <robin@icewind.nl>
Signed-off-by: Robin Appelman <robin@icewind.nl>
Signed-off-by: Robin Appelman <robin@icewind.nl>
icewind1991
force-pushed
the
single-query-search
branch
from
June 14, 2021 14:18
097fc68
to
ca4a931
Compare
Signed-off-by: Robin Appelman <robin@icewind.nl>
icewind1991
force-pushed
the
single-query-search
branch
from
June 14, 2021 14:23
ca4a931
to
362cb2a
Compare
juliusknorr
approved these changes
Jun 16, 2021
Can this be backported to 21? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes file search from having each storage's cache perform the cache to asking each cache for how to filter search results, combining all filters from every cache and running the search in a single query.
The results are then passed to the caches again to allow post-processing before finally turning them into the final result objects.
This way there is only a single query required for the search no matter how many storages a user has access to, this does come at the cost of a more complex query but it should still be a good improvement overall