-
Notifications
You must be signed in to change notification settings - Fork 1
[b/328439250] Remove NULL expectations from boolean columns #2
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
base: master
Are you sure you want to change the base?
Conversation
Dimensions of type YESNO in LookML will never return NULL, so when we select a boolean column in the SQL Interface, we should never expect NULL.
| </schema> | ||
| <tuple> | ||
| <value>%null%</value> | ||
| </tuple> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not familiar with the datasets, is this removing an expected column value or row value?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's removing a single cell from the expected results. you can see in the above tag the name of the column you're removing a row from.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the info @tanclary, sorry missed checking information you added to the bug.
LGTM for the change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No worries thanks for looking y'all 👍
Anthrino
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to confirm @tanclary, did we find a reason why Looker isn't returning these Null values?
Might be worth mentioning the reason we have to remove these from expected results.
Yes it's in the commit message and on the bug, tl:dr YESNO fields don't allow return NULL. |
No description provided.