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
From our understanding, separate json files are created for each combination of dimension in which data needs to be visualized and there is no querying layer as such for viz.
How does this work with multi-select filters?
Are json files created for each combination of multi-select filters?
This seems to significantly blow up scale of data stored. For each 'feature/column' there are $2^{n}$ -1 combinations of multi-select filters available where n is the number of categories in that column.
The text was updated successfully, but these errors were encountered:
From our understanding, separate json files are created for each combination of dimension in which data needs to be visualized and there is no querying layer as such for viz.$2^{n}$ -1 combinations of multi-select filters available where n is the number of categories in that column.
How does this work with multi-select filters?
Are json files created for each combination of multi-select filters?
This seems to significantly blow up scale of data stored. For each 'feature/column' there are
The text was updated successfully, but these errors were encountered: