nicolaspi opened a new issue, #23880:
URL: https://github.com/apache/superset/issues/23880
A cross filter on BIGINT column may format the WHERE clause in charts into
float number:
`WHERE params_hash IN (-3.297260625658751e+18)`
Should be:
`WHERE params_hash IN (-3297260625658750778)`
#### How to reproduce the bug
1. Make a cross filter on a BIGINT column.
2. Filter on a failing value (not all values are failing). e.g.
-3297260625658750778
3. Cross filtered chart fail to display data because of bad formatting of
the value.
### Expected results
The cross filtered chart should have a well-formed WHERE clause:
`WHERE params_hash IN (-3297260625658750778)`
and the chart output right data.
### Actual results
The cross filtered chart has a malformed WHERE clause:
`WHERE params_hash IN (-3.297260625658751e+18)`
and the chart output no data.
### Environment
(please complete the following information):
- browser type and version: Chrome Version 112.0.5615.165 (Official Build)
(64-bit)
- superset version: docker-compose up
- python version: 3.10
- node.js version: `v14.21.1`
- any feature flags active: `FEATURE_FLAGS = {"ALERT_REPORTS": True,
"DASHBOARD_CROSS_FILTERS": True, "ENABLE_TEMPLATE_PROCESSING": True}`
### Checklist
Make sure to follow these steps before submitting your issue - thank you!
- [X] I have checked the superset logs for python stacktraces and included
it here as text if there are any.
- [X] I have reproduced the issue with at least the latest released version
of superset.
- [X] I have checked the issue tracker for the same issue and I haven't
found one similar.
### Additional context
Add any other context about the problem here.
--
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]
