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

Error when enabling GENERIC_CHART_AXES feature in Apache Superset #24527

Closed
vvsiv opened this issue Jun 27, 2023 · 6 comments
Closed

Error when enabling GENERIC_CHART_AXES feature in Apache Superset #24527

vvsiv opened this issue Jun 27, 2023 · 6 comments

Comments

@vvsiv
Copy link

vvsiv commented Jun 27, 2023

Hello there,

I have encountered an issue when enabling the GENERIC_CHART_AXES feature in Apache Superset. The problem is with the following chart types: Calendar Heatmap, Event Flow, Horizon Chart, Paired t-test Table.

When trying to create a new chart of these types or editing an existing one, I receive the following error message: "Datetime column not provided as part table configuration and is required by this type of chart."

Steps to reproduce:

Enable GENERIC_CHART_AXES feature in Apache Superset.
Attempt to create or edit a chart of the types: Calendar Heatmap, Event Flow, Horizon Chart, Paired t-test Table.
Expected result:
The charts should be created/edited without any errors.

Actual result:
The error "Datetime column not provided as part table configuration and is required by this type of chart" is displayed.
2023-06-27 14 25 07

This issue prevents me from utilizing these specific chart types while using the GENERIC_CHART_AXES feature. Any assistance with resolving this issue would be greatly appreciated.

Thank you for your help.

@sfirke
Copy link
Member

sfirke commented Jun 27, 2023

What version of Superset are you using?

@vvsiv
Copy link
Author

vvsiv commented Jun 27, 2023

I am using Apache Superset version 2.1.

@sfirke
Copy link
Member

sfirke commented Jul 10, 2023

I can confirm this issue on 2.1.0 for these chart types, agreed this seems like a bug. Seems related to #23766.

@sfirke
Copy link
Member

sfirke commented Jul 10, 2023

I wonder if this fixed it, merged on May 1: #23865

@sfirke
Copy link
Member

sfirke commented Sep 8, 2023

@vvsiv are you able to test this with the just-released version 2.1.1?

@rusackas
Copy link
Member

Hi there, and sorry this has gone quiet for so long. We're no longer supporting Superset 2.x or prior, and it's been a while since this thread saw any activity, so I'm closing this as stale. If it is still an issue in Superset 3.x (where this feature flag is on by default now!), we can re-open this, or feel free to open a new issue with updated context.

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

3 participants