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.

Sign up for GitHub

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

Jump to bottom

line visualization is recommended but timestamps are getting parsed wrong #2526

Closed
camsaul opened this issue May 4, 2016 · 0 comments
Closed

line visualization is recommended but timestamps are getting parsed wrong #2526

camsaul opened this issue May 4, 2016 · 0 comments
Assignees
@tlrobinson
Labels
Type:Bug Product defects Visualization/
Milestone
0.17.1

Comments

@camsaul
Copy link
Member

camsaul commented May 4, 2016

This is on 0.18-SNAPSHOT. Similar to #2183 / #2379.

I have (wacky) data like this:

screen shot 2016-05-03 at 5 20 57 pm

Line is a recommended visualization type:

screen shot 2016-05-03 at 5 20 35 pm

But the timestamp values are wrong...

screen shot 2016-05-03 at 5 20 51 pm
screen shot 2016-05-03 at 5 20 40 pm

?

So not sure what the fix for this is but I guess we should either show the "wrong visualization type" error message for this situation as well or fix the timestamp parsing bug
@camsaul camsaul added Type:Bug Product defects Visualization/ labels May 4, 2016
@camsaul camsaul added this to the 0.17.1 milestone May 4, 2016
@tlrobinson tlrobinson self-assigned this May 5, 2016
@tlrobinson tlrobinson mentioned this issue May 9, 2016
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tlrobinson tlrobinson

Labels
Type:Bug Product defects Visualization/
Projects
None yet
Milestone
0.17.1
Development

No branches or pull requests
3 participants
@tlrobinson @camsaul @agilliland