Unable to query against columns with dots in their names #240
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
|
👍 just had the same issue, we are storing columns with dot inside their names (since influxdb does not support nested objects) we can request them all but not a subset of them. |
Don't always assume that column names with dots have the format `table_name.column_name`. Instead, we check whether `table_name` exists and if it doesn't we treat the full name as a column name.
pauldix
added a commit
that referenced
this pull request
Feb 10, 2014
Unable to query against columns with dots in their names
|
Thanks for the merge into master @pauldix ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is some problem querying columns that have dots (and I guess other 'special' symbols in their names).
I've created a single point with two columns - a.1 & a.2 in a series called foo.
When I request all the data (*), I do get proper result:
curl 'http://localhost:8086/db/metrics/series?u=root&p=root&q=select+*+from+foo'
[{"name":"foo","columns":["time","sequence_number","a.1","a.2"],"points":[[1391713357450,487020001,1,2]]}]
When I request the first column (a.1) everything still looks good:
curl 'http://localhost:8086/db/metrics/series?u=root&p=root&q=select+a.1+from+foo'
[{"name":"foo","columns":["time","sequence_number","a.1"],"points":[[1391713357450,487020001,1]]}]
When I request the second column (a.2) though, unexpected stuff happens (data for a.1 is returned):
curl 'http://localhost:8086/db/metrics/series?u=root&p=root&q=select+a.2+from+foo'
[{"name":"foo","columns":["time","sequence_number","a.1"],"points":[[1391713357450,487020001,1]]}]