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.
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
fix(approx_topk): Map approx_topk operation in all cases #16131
fix(approx_topk): Map approx_topk operation in all cases #16131
Changes from 2 commits
8508cc7
8b259f8
2877839
967ad7a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Are we sure these are shardable? Is this an orthogonal change to the above?
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.
As far as I understand, we should treat them the same way as the arithmetic operations above. There's no special logic for those operations, they just get mapped to queriers and combined as usual.
I don't think sharding a approx_topk query containing a comparison will change the result, as far as I can see, though I don't have any proof beyond the existing tests that it is valid to do so.
If you prefer I can remove this change and those types of queries will fall into the "not shardable" logic instead. I've tested it locally and it does seem to give correct results - WDYT?
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.
Hm, so I'd push the operator don to each shard because it's filtering out the metrics. Does that makes sense? As in:
should be
and not
I think sharding these is a little more evolved and should be a separarte PR.