-
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
command "select * from measurement" do not return all the columns #3045
Comments
@huangyukun2012 To understand what might have happened we need to see how you are creating your data. Can you provide some examples of your write statements? |
@beckettsean
|
@huangyukun2012 your insert statements have a strange and I believe unintended syntax. For the line protocol, whitespace has very specific meaning. Whitespace separates the measurement and tag set from the field set, and the field set from the timestamp. The syntax is
Your point, Please see #2696 for a more detailed write-up of the line protocol syntax. Website documentation is coming soon. |
@beckettsean I want to store CDN and Device as both tags and fields, So I get the error. Does this mean that tags and fields should not have the same name? |
No, they should not use the same name. Field and tag names sets must never On Tuesday, June 23, 2015, Yukun Huang notifications@github.com wrote:
|
See #2615 for more on field keys and tag keys must be mutually exclusive. @huangyukun2012 What is your use case that you want the values to be stored as both fields and tags? I don't see any benefit to duplicating the data. Most likely we can help you solve your challenge in a different way. |
@beckettsean The situation is:I must query the database base with |
i have been doing the same thing. the tags are part of the data i need to consume so i've been duplicating it as a field and as a tag because i hadn't found a better way to do this. would be glad to know of a better approach if it exists. EDIT: this was based on what was possible in approx rc28. things may have improved but i don't recall seeing anything. |
@neonstalwart @huangyukun2012 Can one of you open a new issue describing the reason you can't write this data as only tags or only fields? |
@beckettsean Ok, I will open a new issue later~ |
when we use the command "select * from MEASUREMENT", we want to get all the columns. However, there is something wrong with my influxdb. The following is the test case:
my influxdb version is
0.9.0
, build from source code, the commit id is9f45a9eea3017e372711d3ae5949056d53a4ba6a
, the machine is MAC.As you can see, the tag keys and field keys duplicated in my measurement. This is the reason why I get the bug?
The text was updated successfully, but these errors were encountered: