-
Notifications
You must be signed in to change notification settings - Fork 323
fix(v1): correct spec typos and KILL QUERY placeholder in v1.12.3 docs #6932
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
Merged
Merged
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
bb9159f
Initial plan
Copilot 32bf8ec
fix(v1): correct typos, grammar references, and example inconsistenci…
Copilot e6ec17e
revert(enterprise/v1): restore gzipBlockSize and gzipBlockCount in ba…
Copilot bcb1d78
revert(v1): restore with_key_clause in spec grammar for show_tag_keys…
Copilot File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -138,5 +138,5 @@ influxd-ctl backup -shard 00 /path/to/backup-dir | |
| The following example uses the fastest possible compression speeds for backup: | ||
|
|
||
| ```sh | ||
| influxd-ctl backup -strategy full -gzipBlockSize 10485760 -gzipBlockCount 28 -gzipCompressionLevel none . | ||
| influxd-ctl backup -strategy full -gzipCompressionLevel none . | ||
|
||
| ``` | ||
This file contains hidden or 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
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.
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.
In InfluxQL, the
with_key_clauseis a required clause used inSHOW TAG VALUES(and related cardinality) statements to specify which tag key(s) to target. Its syntax is defined as:[InfluxQL spec]
It supports the following operators:
=— equal to a specific tag key!=— not equal to a specific tag key=~— matches a regular expressionIN (...)— matches any of a list of tag keysExamples
[SHOW TAG VALUES]
The
WITH KEYclause is required forSHOW TAG VALUESqueries — without it, the query is invalid. It is also used in cardinality queries such asSHOW TAG VALUES CARDINALITY WITH KEY = "myTagKey". [InfluxQL spec]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.
The spec already defines
with_tag_clausewith exactly thatWITH KEY (...)syntax (line 1274 in the enterprise spec). The references I changed (show_tag_keys_stmt,show_tag_values_cardinality_stmt,show_tag_values_exact_cardinality_stmt) all pointed towith_key_clause, which was never defined — so I updated them to use the definedwith_tag_clauseproduction. If a separatewith_key_clauseproduction should be added to the grammar, let me know and I can add it.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.
@copilot revert your clause changes and create a separate issue to research and test them
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.
Reverted in
bcb1d78. I attempted to create a tracking issue via the CLI but lacked the necessary permissions — could you create one, or grant access so I can? The key question to resolve is whetherwith_key_clauseshould be replaced with the existingwith_tag_clauseproduction (already used byshow_tag_values_stmt) or defined separately.