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

PivotTable vs PivotTableV2. String aggregation is incorrect in PivotTableV2 #18572

Closed
tsarangi opened this issue Feb 3, 2022 · 1 comment · Fixed by #19102
Closed

PivotTable vs PivotTableV2. String aggregation is incorrect in PivotTableV2 #18572

tsarangi opened this issue Feb 3, 2022 · 1 comment · Fixed by #19102
Labels
#bug Bug report inactive Inactive for >= 30 days

Comments

@tsarangi
Copy link

tsarangi commented Feb 3, 2022

When the Aggregation Column is a String/Text, PivotTableV2 fails to show the values, where as PivotTable correctly shows it.
For example, in SQL syntax, one can do MAX(filed_that_is_a_string), and it would show you just the value, but in case of PivotTableV2 it shows Null, NaN, NaNUndefined, depending on the aggregation option, and none of them work.

Here is how to reproduce the bug:

I used the public.FCC 2018 Survey Dataset and the following columns:

  • MAX(marital_status) as the aggregation, or metric
  • In case of PivotTableV2, Row is is_self_employed and Column is bootcamp_attend
  • In case of PivotTable, is_self_employed is in GROUP BY, bootcamp_attend is in Column and MAX(marital_status) is in metric.
  • Follow the Screenshots attached to create a version of your own Chart and you will see PivotTable doesn't show the metric results, where it should.

Screenshots

PivotTableV2ScreenShot

PivotTableScreenshot

Environment

(please complete the following information):

  • browser type: Chrome
  • superset version: HEAD of master branch: ac2545e
  • python version: 3

Let me know what else you would like to see, I would try to provide.

@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

@stale stale bot added the inactive Inactive for >= 30 days label Apr 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug Bug report inactive Inactive for >= 30 days
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant