dosubot[bot] commented on issue #36401: URL: https://github.com/apache/superset/issues/36401#issuecomment-3605436812
<!-- Greeting --> Hi @jongkookson! I'm [Dosu](https://go.dosu.dev/dosubot) and Iām helping the superset team. <!-- Answer --> This is a confirmed regression in Superset 5.0.0: mixing BigInt and Number types in the frontend (especially with ECharts) causes a `TypeError` when rendering charts with very large integers. This was not present in 4.1.4 and earlier. Recent fixes in Superset (after August 2025) address BigInt serialization and rendering by converting BigInt values to strings before comparison and serialization in filters and charts, and by improving backend JSON utilities to handle BigInt safely ([details](https://github.com/apache/superset/issues/35087)). These fixes are not included in 5.0.0. For Superset 5.0.0, the most reliable workaround is to cast large integer fields to string in your SQL queries, for example: `SELECT CAST(a AS TEXT) AS a, CAST(b AS TEXT) AS b ...`. This avoids the frontend mixing BigInt and Number types. Some users report partial success by casting to BIGINT, but if the frontend still receives mixed types, the error can persist ([discussion](https://github.com/apache/superset/issues/33556)). If possible, upgrade to a Superset commit after August 2025 to get the latest BigInt handling fixes directly. If you need a frontend patch, you would need to ensure all large values are stringified before rendering or serialization. There is no documented configuration workaround beyond casting to string or BIGINT in SQL. Persistent issues may require frontend code modification or upgrading to a version with the relevant fixes. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/7c2dfd37-0345-406c-a53f-bb28f01db6c5?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/7c2dfd37-0345-406c-a53f-bb28f01db6c5?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/7c2dfd37-0345-406c-a53f-bb28f01db6c5?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/7c2dfd37-0345-406c-a53f-bb28f01db6c5?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/7c2dfd37-0345-406c-a53f-bb28f01db6c5?feedback_type=hallucination) | [Report š](https://app.dosu.dev/response-feedback/7c2dfd37-0345-406c-a53f-bb28f01db6c5?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/7c2dfd37-0345-406c-a53f-bb28f01db6c5?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=This%20is%20a%20confirmed%20regression%20in%20Superset%205.0.0%3A%20mixing%20BigInt%20and%20Number%20types%20in%20the%20frontend%20%28especially%20with%20ECharts%29%20causes%20a%20%60TypeError%60%20when%20rendering%20charts%20with%20very%20large%20integers.%20This%20was%20not%20present%20in%204.1.4%20and%20earlier.%0A%0ARecent%20fixes%20in%20Superset%20%28after%20August%202025%29%20address%20BigInt%20serialization%20and%20rendering%20by%20converting%20BigInt%20values%20to%20strings%20before%20comparison%20and%20serialization%20in%20filters%20and%20charts%2C%20and%20by%20improving%20backend%20JSON%20utilities%20to%20handle%20BigInt%20safely%20%28%5Bdetails%5D%28https%3A//github.com/apache/superset/issues/35087%29%29.%20These%20fixes%20are%20not%20in cluded%20in%205.0.0.%0A%0AFor%20Superset%205.0.0%2C%20the%20most%20reliable%20workaround%20is%20to%20cast%20large%20integer%20fields%20to%20string%20in%20your%20SQL%20queries%2C%20for%20example%3A%20%60SELECT%20CAST%28a%20AS%20TEXT%29%20AS%20a%2C%20CAST%28b%20AS%20TEXT%29%20AS%20b%20...%60.%20This%20avoids%20the%20frontend%20mixing%20BigInt%20and%20Number%20types.%20Some%20users%20report%20partial%20success%20by%20casting%20to%20BIGINT%2C%20but%20if%20the%20frontend%20still%20receives%20mixed%20types%2C%20the%20error%20can%20persist%20%28%5Bdiscussion%5D%28https%3A//github.com/apache/superset/issues/33556%29%29.%0A%0AIf%20possible%2C%20upgrade%20to%20a%20Superset%20commit%20after%20August%202025%20to%20get%20the%20latest%20BigInt%20handling%20fixes%20directly.%20If%20you%20need%20a%20frontend%20patch%2C%20you%20would%20need%20to%20ensure%20all%20large%20values%20are%20stringified%20before%20rendering%20or%20serialization.%0A%0AThere%20is%20no%20documented%20configuration%20workaroun d%20beyond%20casting%20to%20string%20or%20BIGINT%20in%20SQL.%20Persistent%20issues%20may%20require%20frontend%20code%20modification%20or%20upgrading%20to%20a%20version%20with%20the%20relevant%20fixes.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/36401) -- 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]
