geido opened a new issue, #32042:
URL: https://github.com/apache/superset/issues/32042

   ### Bug description
   
   ## Description
   When creating a Partition Chart with more than two dimensions (e.g., 
`category`, `subcategory`, `sub_subcategory`), the chart renders entries 
incorrectly. Specifically:
   
   - Entries that belong to specific subcategories (`a.1.1`) are being grouped 
under unrelated categories (`a.a.2`), which is incorrect.
   - This issue causes misleading chart visualizations.
   
   ## How to reproduce the bug
   1. Use the following dataset or SQL query:
   
   `SELECT 'a' AS category, 'a.1' AS subcategory, 'a.1.1' AS sub_subcategory
   UNION
   SELECT 'a' AS category, 'a.2' AS subcategory, 'a.2.1' AS sub_subcategory
   UNION
   SELECT 'a' AS category, 'a.2' AS subcategory, 'a.2.2' AS sub_subcategory`
   
   2. Create a Partition Chart with it suing the following configuration:
       1. Set `COUNT(*)` as the metric.
       2. Use `category`, `subcategory`, and `sub_subcategory` as dimensions.
   3. Generate the Partition Chart.
   
   
   ## Expected results
   Subcategories (`a.1.1`) should appear under their respective parent 
`subcategory` (e.g., `a.1`).
   
   ## Actual results
   - The `a.1.1` entry incorrectly shows up under `a.a.2`.
   - Entries from different subcategories overlap or are misattributed in the 
visualization.
   
   ## Known Workarounds
   No workarounds are currently known
   
   ### Screenshots/recordings
   
   
![Image](https://github.com/user-attachments/assets/9c74e1a9-b77a-4c65-9f76-90ce004c261a)
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.9
   
   ### Node version
   
   18 or greater
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [x] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [x] 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.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to