-
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
superset can not know the string/varchar columns from impala table #2973
Comments
Sure this is an issue in superset and not in the sqlalchemy dialect / plumbing? |
@xrmx I am a superset beginner, no idea about the problem.Do you use superset on impala table that has the string/varchar columns and succeed? |
i had the same issue with 0.18.5 |
Same issue. I'm on 0.18.5 as well. This maybe another issue, but Time Grains don't show for Impala as well. |
I wonder if the Do you see stack traces in your log when saving a Impala table? If so please paste it here. If not that means it's coming out as |
@JImBurris about time grains, they haven't been contributed yet for Impala. Someone needs to send a PR with a DBEngineSpec with time grains defined for impala, it's as simple as: |
Here, can someone that has impala test this? |
Notice: this issue has been closed because it has been inactive for 264 days. Feel free to comment and request for this issue to be reopened. |
Make sure these boxes are checked before submitting your issue - thank you!
Superset version
0.18.4
Expected results
when Add Sqla Table, superset can get all right columns from impala table
Actual results
when Add Sqla Table, superset can not know the string/varchar columns from impala table
Steps to reproduce
1.have impala table:
2.Add Database from impala
3.Add Sqla Table
edit table->list table column, I find that the string/varchar columns can not be known by superset
The text was updated successfully, but these errors were encountered: