-
Notifications
You must be signed in to change notification settings - Fork 14k
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 import "parse dates" should be more flexible #4637
Comments
xrmx
added a commit
to xrmx/superset
that referenced
this issue
Mar 23, 2018
Instead of a boolean which has way less chances to work. While at it add a proper label for the "con" field. Fixes apache#4637
graceguo-supercat
pushed a commit
that referenced
this issue
Mar 23, 2018
Instead of a boolean which has way less chances to work. While at it add a proper label for the "con" field. Fixes #4637
michellethomas
pushed a commit
to michellethomas/panoramix
that referenced
this issue
May 24, 2018
…4639) Instead of a boolean which has way less chances to work. While at it add a proper label for the "con" field. Fixes apache#4637
wenchma
pushed a commit
to wenchma/incubator-superset
that referenced
this issue
Nov 16, 2018
…4639) Instead of a boolean which has way less chances to work. While at it add a proper label for the "con" field. Fixes apache#4637
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Make sure these boxes are checked before submitting your issue - thank you!
Superset version
latest master 97afcd5
Expected results
Dates should be imported as dates
Actual results
Dates are imported as text
Steps to reproduce
With actual code parse_dates is a boolean and if true it tries to parse the index:
But if i pass the column index or name it works fine:
So i think parse_dates should not be a boolean field but a text field that gets converted to a list of string
The text was updated successfully, but these errors were encountered: