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.
trie: supporting nested value list queries #475
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: master
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
trie: supporting nested value list queries #475
Changes from all commits
aa7fcf5File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
Value list (i.e. curl braces) in go-carbon queries is a tricky business. filepath.Glob, trigram, and trie index all have to work around the issue one way or the other. Currently, all the three query paths depends on `*CarbonserverListener.expandGlobBraces` to to perform the expansion. However, it currently does not support nested value lists like `{a,b,c,x.{a,b,c}}`. Unlike filepath.Glob and trigram, trie index does not need full expansion, it only needs expansion if a query contains nested values that are hierarchical (i.e. containing a dir node, another i.e., a dot). This is also partially due to the current implementation of how trie index handles hierarchical queries. To be more specific, trieIndex.query does not support queries like x.y.z.{a,nested.subquery}`, therefore, a query like that would be expanded by `*CarbonserverListener.expandGlobBraces` as `x.y.z.a` and `x.y.z.nested.subquery`. However, the current implementation does not support nested value lists like `x.y.z.{a,nested.subquery.{a,b,c}}`. This patch introduces a more through and proper (TM) value list query parser and rewriter for supporting all expansion cases (hopefully). Like most of the other improvements, only the trie index is supported for now. Unlike `*CarbonserverListener.expandGlobBraces`, *CarbonserverListener.expandGlobBracesForTrieIndex would only expand value list that contains dir/hierarchical nodes. For example, `x.y.z.{a,b,nested.subquery.{a,b,c}}` is rewritten as `x.y.z.{a,b}` and `x.y.z.nested.subquery.{a,b,c}`, because trie index can handle non-hierarchical value lists natively. We should also try to introduce a new expand function that can do full expansion to replace `*CarbonserverListener.expandGlobBraces`.Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Uh oh!
There was an error while loading. Please reload this page.