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

[Filter Box] Boolean values show up blank in selector #4297

Closed
3 tasks
vylc opened this issue Jan 26, 2018 · 4 comments · Fixed by #4651
Closed
3 tasks

[Filter Box] Boolean values show up blank in selector #4297

vylc opened this issue Jan 26, 2018 · 4 comments · Fixed by #4651
Assignees

Comments

@vylc
Copy link

vylc commented Jan 26, 2018

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

Superset version

Expected results

Should show true/false

Actual results

Shows blank

Steps to reproduce

Add boolean type column to filter section

screen shot 2018-01-25 at 7 00 35 pm

@mistercrunch
Copy link
Member

Presto? Redshift?

@circld
Copy link

circld commented Mar 19, 2018

Also experiencing this behavior on v0.22.1 Postgres tables for any BOOLEAN columns used in a Filter Box slice.

@mistercrunch mistercrunch self-assigned this Mar 19, 2018
@jakromm
Copy link

jakromm commented Mar 19, 2018

I'm sure the root cause on this is different, but since you are addressing this code area it might be an easy fix. When exploring a slice and "Enable Filter Select" is enabled, the NULL case in the drop down also shows up as Empty like is shown above. There also doesn't seem to be a way to filter for IS NULL, if you try to use the 'in' predicate it creates an empty set and simply does 1 != 1 (or however you have empty_in_strategy configured for the connection).

@mistercrunch
Copy link
Member

related as prerequisite: #4651

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

Successfully merging a pull request may close this issue.

4 participants