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

Drill-to-detail not update the underlying data #30952

Closed
3 tasks done
rithysokun opened this issue Nov 18, 2024 · 3 comments
Closed
3 tasks done

Drill-to-detail not update the underlying data #30952

rithysokun opened this issue Nov 18, 2024 · 3 comments

Comments

@rithysokun
Copy link

rithysokun commented Nov 18, 2024

Bug description

In version 3.0.0 . I click feature drill-to-detail behind the pie chart but the chart does not render and update the data in the table when using the drill-to-detail .
However, when click edit chart -> sample -> the data is updated just the same as result in sql lab .
Is this a bug in Superset version 3.0.0?

Screenshots/recordings

q-com1

  • above screenshot is from SQL lab query
qcom2.mov

Superset version

3.1.3

Python version

3.9

Node version

16

Browser

Chrome

Additional context

Expected behaviour

The result from "drill-to-detail" feature should be the same as the result of the query shown in SQL lab . Store ID : 176 is missing in the "drill-to-detail" table

Checklist

  • I have searched Superset docs and Slack and didn't find a solution to my problem.
  • I have searched the GitHub issue tracker and didn't find a similar bug report.
  • I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Copy link

dosubot bot commented Nov 18, 2024

Hey @rithysokun! 👋 I'm here to help you with any bugs, questions, or contributions you have for Superset. Let's tackle this together!

The issue you're experiencing with the 'drill-to-detail' feature not updating the underlying data in Superset version 3.0.0 could be due to several conditions under which this feature fails to function correctly:

  1. Database Settings: If the database settings have disable_drill_to_detail set to true, the feature will not work [1].

  2. No Aggregations: The feature requires the chart to group data by dimension value. If there are no aggregations (metrics), it will be disabled [1].

  3. No Filters: The feature needs filters to be applied. Without filters, it cannot drill down by dimension value [1].

  4. Unsupported Chart Type: If the chart type does not support the drill-to-detail behavior, the feature will not be available [1].

  5. No Dimensions: If the chart does not group data by dimension value, the feature will be disabled [2].

Ensure that these conditions are met in your setup. If the issue persists despite meeting these conditions, it might be a bug specific to your environment or configuration.

To continue talking to Dosu, mention @dosu.

@rithysokun
Copy link
Author

@dosu all the above conditions are met in my context . Are there anything to fix?

Copy link

dosubot bot commented Nov 18, 2024

If all the conditions mentioned are met and the issue persists, it might be helpful to check the following:

  1. Logs and Debugging: Review the Superset logs for any errors or warnings that might provide more insight into why the 'drill-to-detail' feature isn't working as expected. Look for any JavaScript errors in the browser's console as well.

  2. Version Differences: Since you mentioned using version 3.0.0, consider testing the feature on a newer version, like 3.1.3, to see if the issue persists. There might be bug fixes or improvements in the newer version that address this problem.

  3. Code Review: Examine the DrillDetailMenuItems component and related code paths to ensure there are no custom modifications or overrides that might affect its behavior [1].

  4. Dependencies: Ensure that all dependencies and external libraries are up to date and compatible with your Superset version. Sometimes, outdated or incompatible libraries can cause unexpected behavior.

If none of these steps resolve the issue, it might be worth considering if there are any environment-specific factors or custom configurations that could be influencing the behavior.

To continue talking to Dosu, mention @dosu.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant