dosubot[bot] commented on issue #33556:
URL: https://github.com/apache/superset/issues/33556#issuecomment-2911755584
<!-- Answer -->
You've already tried casting to BIGINT, but the largest value ("prd") is
still missing from your pie chart. This suggests the issue is not just with SQL
casting or JavaScript number limits—your value is within the safe integer range.
There are known regressions and fixes in Superset related to BIGINT and
large number rendering in charts, including pie charts. For example, there was
a BIGINT rendering regression in chartAction and a fix for big-number display
issues in ECharts, which is the charting library used by Superset pie charts
[[source]](https://github.com/apache/superset/blob/master/superset-frontend/CHANGELOG.md).
These issues could cause large values to be omitted or displayed incorrectly.
Since you are on Superset 3.0.0, it's possible you are encountering a bug
that was fixed in a later release. The changelogs reference fixes for
big-number display issues, but there is no specific configuration or workaround
documented beyond casting to BIGINT
[[source]](https://github.com/apache/superset/blob/master/superset-frontend/CHANGELOG.md).
If you have already cast your metric to BIGINT and the problem persists,
here are a few things to check:
- Make sure the query result actually includes the "prd" row with the
expected value.
- Try exporting the chart data to CSV to confirm that "prd" is present in
the data Superset receives.
- Check if there are any frontend errors in the browser console when
rendering the chart.
- If possible, test with a more recent version of Superset to see if the
issue is resolved, as there have been fixes for similar problems.
If none of these steps help, this may be a bug that still exists in your
version. There is no documented configuration workaround beyond what you've
already tried. If you can confirm "prd" is present in the query result but
missing in the chart, it is likely a frontend rendering issue related to large
numbers.
<!-- Dosu Comment Footer -->
*To reply, just mention my name [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do?
[Good](https://app.dosu.dev/response-feedback/74304a45-ef17-4100-9496-0c81b81b2403?feedback_type=great_response)
|
[Irrelevant](https://app.dosu.dev/response-feedback/74304a45-ef17-4100-9496-0c81b81b2403?feedback_type=irrelevant_answer)
|
[Incorrect](https://app.dosu.dev/response-feedback/74304a45-ef17-4100-9496-0c81b81b2403?feedback_type=incorrect_sources)
|
[Verbose](https://app.dosu.dev/response-feedback/74304a45-ef17-4100-9496-0c81b81b2403?feedback_type=too_verbose)
|
[Hallucination](https://app.dosu.dev/response-feedback/74304a45-ef17-4100-9496-0c81b81b2403?feedback_type=hallucination)
| [Report
🐛](https://app.dosu.dev/response-feedback/74304a45-ef17-4100-9496-0c81b81b2403?feedback_type=bug_report)
|
[Other](https://app.dosu.dev/response-feedback/74304a45-ef17-4100-9496-0c81b81b2403?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [!
[Share on
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/33556)
--
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]
