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

TableViz raise Unexpected error when table include null value #5604

Closed
3 tasks done
Wujiao233 opened this issue Aug 11, 2018 · 5 comments
Closed
3 tasks done

TableViz raise Unexpected error when table include null value #5604

Wujiao233 opened this issue Aug 11, 2018 · 5 comments

Comments

@Wujiao233
Copy link

Make sure these boxes are checked before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if any
  • I have reproduced the issue with at least the latest released version of superset
  • I have checked the issue tracker for the same issue and I haven't found one similar

when table include number type columns and the value is null , The TableViz cannot display this table when these columns be selected in NOT GROUPED BY

Superset version

0.26.3 On centos7 + Python 3.6.5

Expected results

Actual results

Unexpected error.

Steps to reproduce

Table DDL:
CREATE TABLE testt ( id int(11) NOT NULL AUTO_INCREMENT, name varchar(255) DEFAULT NULL, value int(255) DEFAULT NULL, PRIMARY KEY (id) ) ENGINE=InnoDB AUTO_INCREMENT=5 DEFAULT CHARSET=utf8;
Data:

id name value
1 aaa 1
2 bbb
3 ccc 3
4 ddd

And choose these three columns in TableViz's NOT GROUPED BY selector.

@villebro
Copy link
Member

This is a duplicate of #5353

@villebro
Copy link
Member

@Wujiao233 This was reported on 0.26.3 but the PR is against master, can you verify that you are able to get the same error on master also?

@Wujiao233
Copy link
Author

the master is ok...but i think it's not a good idea to fill number type null to 0 .In some case null is not mean 0 .

@stale
Copy link

stale bot commented Apr 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

@stale stale bot added the inactive Inactive for >= 30 days label Apr 10, 2019
@villebro
Copy link
Member

@Wujiao233 this issue has been resolved and can be closed

@stale stale bot removed the inactive Inactive for >= 30 days label Apr 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants