-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[0.10.0] SHOW TAG VALUES does not work on cluster #5593
Milestone
Comments
Closed
I'm going to start converting this to use the new query engine. It will depend on #5811 being merged first though. |
jsternberg
added a commit
that referenced
this issue
Feb 26, 2016
jsternberg
added a commit
that referenced
this issue
Mar 4, 2016
`SHOW TAG VALUES` output has been modified to print the measurement name for every measurement and to return the output in two columns: key and value. An example output might be: > SHOW TAG VALUES WITH KEY IN (host, region) name: cpu --------- key value host server01 region useast name: mem --------- key value host server02 region useast `measurementsByExpr` has been taught how to handle reserved keys (ones with an underscore at the beginning) to allow reusing that function and skipping over expressions that don't matter to the call. Fixes #5593.
jsternberg
added a commit
that referenced
this issue
Mar 6, 2016
`SHOW TAG VALUES` output has been modified to print the measurement name for every measurement and to return the output in two columns: key and value. An example output might be: > SHOW TAG VALUES WITH KEY IN (host, region) name: cpu --------- key value host server01 region useast name: mem --------- key value host server02 region useast `measurementsByExpr` has been taught how to handle reserved keys (ones with an underscore at the beginning) to allow reusing that function and skipping over expressions that don't matter to the call. Fixes #5593.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SHOW TAG VALUES
does not return the correct results from all nodes in a fully replicated cluster (default config values).Node 1:
Node 2 (after all commands on node 1 have completed):
Node 3 (after all commands on node 1 have completed):
The text was updated successfully, but these errors were encountered: