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

Chart filter options are not populated for datasets with normalize column enabled #26198

Closed
3 tasks done
Vitor-Avila opened this issue Dec 6, 2023 · 0 comments
Closed
3 tasks done

Comments

@Vitor-Avila
Copy link
Contributor

Vitor-Avila commented Dec 6, 2023

For engines that support column de-normalization, it's possible to opt-out by enabling column normalization. This is enabled by default to all datasets created prior to the implementation of column denormalization. For more context, check below PRs:

Chart filters are not displaying options for datasets that have column normalization enabled.

How to reproduce the bug

  1. Create a dataset powered by an engine that supports column de-normalization (such as Snowflake). Note that:
    a. All columns are uppercase.
    b. Column normalization is disabled (under the SETTINGS tab).
  2. Modify the dataset, and enable column normalization.
  3. Save changes.
  4. Modify the dataset again, and sync columns. Note that all columns are now lowercase.
  5. Save changes.
  6. Create a new chart using this dataset, and drop any column in the FILTERS section.

Expected results

Filter values should be populated in the dropdown.

Actual results

The dropdown is empty. The network request to fetch the column values return below 400 error:

Column name {column_name} does not exist

Environment

  • browser type and version: Chrome version 119.0.6045.159.
  • superset version: 0.0.0-dev (running master).
  • python version: 3.9.0
  • node.js version: v16.14.2
  • any feature flags active: not relevant to reproduce the issue

Checklist

  • I have checked the superset logs for python stacktraces and included it here as text if there are 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.
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

1 participant