You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, VUU doesn't have a way to filter for/out missing data. Missing data could be anything from value being null to "" (for string data type).
Preliminary analysis shows that it would be quite tricky on the server as well as the UI to support filtering of null values with our current filter operators. For example, if we try supporting null for = filter, then on the server side the parsing is relatively straightforward, but how would typeahead work for example? Similarly on the UI for example we expect numeric filters to have only valid numeric values, which means re-working our current components to be able to work with numeric as well as null or some special string representation of null? Also, how would we support null values for = filter and not allow it for other operators where is doesn't make sense e.g. order comparison > or <?
Potential Solutions:
One of the potential solutions could be to introduce new filter operator(s) to support filtering of missing or empty data.
For example, we can have two operators is and is not, with possible enum based values MISSING and EMPTY which are then converted to the relevant underlying values null and "" on the server side before applying filters.
Reference: this is also how SQL supports searching for NULL values for example: WHERE column_x IS NULL.
The text was updated successfully, but these errors were encountered:
This is more about missing data i.e. row having a value null or "" for a certain valid column. Currently, we don't have a way to filter for those. For instance, a user wants to see all the rows where price is not missing, for now we can't do this in Vuu.
Feature Request
Description of Problem:
Currently, VUU doesn't have a way to filter for/out missing data. Missing data could be anything from value being
null
to""
(for string data type).Preliminary analysis shows that it would be quite tricky on the server as well as the UI to support filtering of
null
values with our current filter operators. For example, if we try supportingnull
for=
filter, then on the server side the parsing is relatively straightforward, but how would typeahead work for example? Similarly on the UI for example we expect numeric filters to have only valid numeric values, which means re-working our current components to be able to work with numeric as well asnull
or some special string representation ofnull
? Also, how would we supportnull
values for=
filter and not allow it for other operators where is doesn't make sense e.g. order comparison>
or<
?Potential Solutions:
One of the potential solutions could be to introduce new filter operator(s) to support filtering of missing or empty data.
For example, we can have two operators
is
andis not
, with possible enum based valuesMISSING
andEMPTY
which are then converted to the relevant underlying valuesnull
and""
on the server side before applying filters.Reference: this is also how SQL supports searching for
NULL
values for example:WHERE column_x IS NULL
.The text was updated successfully, but these errors were encountered: