This repository has been archived by the owner on Aug 23, 2023. It is now read-only.
Evaluate expressions which involve meta tags at the end #1541
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When evaluating a set of query expressions of which some involve the meta tag index and some do not, then we want to build the initial result set based on those expressions which do not involve it and use the ones that do involve it as filters.
In many cases this can lead to a significant improvement in query latency, because when we build the initial result set based on a meta tag in some cases it can grow to a really large size which then needs to be filtered down (f.e.
datacenter=XYZ).Fixes issue #1534