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

   ### Bug description
   
   ### Summary
   
   There is an issue with filtering numeric values in Superset when values have 
different numbers of digits after the decimal point.
   
   ### Steps to Reproduce
   
   1. Add a filter for a numeric field that contains both integer and decimal 
values (e.g., 21, 21.8, 25.35, etc.).
   
   
![Image](https://github.com/user-attachments/assets/c4f1242e-da6c-40c5-a2ea-d6a023d65912)
   
   2. First select an integer value (for example, 21) in the filter, and then 
fractional values.
   
   
![Image](https://github.com/user-attachments/assets/c4733e54-2347-437a-afd1-642b648732e1)
   
   3. The query returns only the rows where the value is exactly 21 (i.e., 
without any decimal places), excluding 21.8, 25.35, etc.
   
   
![Image](https://github.com/user-attachments/assets/cb73df1f-01d8-4915-bb0b-0560d2c82648)
   
   
![Image](https://github.com/user-attachments/assets/cafae7f9-a22d-401e-9cd2-75c657cccf84)
   
   4. Now, if you select a decimal value first (e.g., 21.8 or 25.35), the 
filtering works as expected, returning all matching rows regardless of decimal 
precision.
   
   
![Image](https://github.com/user-attachments/assets/5c60db1b-833a-4567-af39-4bccb4e6add2)
   
   
![Image](https://github.com/user-attachments/assets/dfcbe4a2-7fb1-4399-a2fe-1e5e30a80567)
   
   ### Expected Behavior
   
   Filtering by numeric value should match all equivalent numeric 
representations (e.g., 21, 21.8, 25.35) regardless of how many decimal places 
are used.
   
   ### Actual Behavior
   
   Filtering is inconsistent depending on whether an integer or decimal value 
is selected first. Selecting an integer leads to an overly strict match that 
excludes decimal representations of the same value.
   
   ### Databases Affected
   
   This issue has been observed across all three databases tested:
   
   - ClickHouse  
   - Impala  
   - PostgreSQL  
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.9
   
   ### Node version
   
   I don't know
   
   ### Browser
   
   Not applicable
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [ ] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [ ] 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