Skip to content
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

CSV output uses previous point value when it should be a null #8343

Closed
ryantxu opened this issue May 1, 2017 · 0 comments
Closed

CSV output uses previous point value when it should be a null #8343

ryantxu opened this issue May 1, 2017 · 0 comments
Assignees
Milestone

Comments

@ryantxu
Copy link

ryantxu commented May 1, 2017

Bug report

X-Influxdb-Version →1.2.2

Steps to reproduce:

  1. /query?q=DROP DATABASE csv_test
  2. /query?q=CREATE DATABASE csv_test
  3. /write?db=csv_test
example a=1,b=2 1465839830100400000 
example a=1 1465839830100500000 

Expected behavior:
I would expect the second point to have a null value for 'b' as it does in the json response:

"values":[["2016-06-13T17:43:50.1004Z",1,2],["2016-06-13T17:43:50.1005Z",1,null]]

Actual behavior:
JSON format gives the expected results, but CSV does not

/query?db=csv_test&q=SELECT * FROM example
Gives:

name,tags,time,a,b,c
example,,1465839830100400000,1,2
example,,1465839830100500000,1,2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants