Praveshvermaa opened a new pull request, #36777:
URL: https://github.com/apache/superset/pull/36777

   Fix native filter boolean column issue where Databricks queries failed due 
to type mismatch. The issue was that boolean values in IN clauses were being 
converted to integers (0/1) instead of boolean literals (True/False), causing 
Databricks to throw a DATATYPE_MISMATCH error.
   
   Changes:
   - Add handle_boolean_in_clause method to DatabricksBaseEngineSpec that uses 
OR conditions with equality checks instead of IN clauses to ensure boolean 
literals are used
   - Modify filter handling in helpers.py to detect boolean columns and use 
engine-specific handling when available
   - Add test to verify boolean IN clause handling
   
   Fixes #36765
   
   <!---
   Please write the PR title following the conventions at 
https://www.conventionalcommits.org/en/v1.0.0/
   Example:
   fix(dashboard): load charts correctly
   -->
   
   ### SUMMARY
   <!--- Describe the change below, including rationale and design decisions -->
   
   ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
   <!--- Skip this if not applicable -->
   
   ### TESTING INSTRUCTIONS
   <!--- Required! What steps can be taken to manually verify the changes? -->
   
   ### ADDITIONAL INFORMATION
   <!--- Check any relevant boxes with "x" -->
   <!--- HINT: Include "Fixes #nnn" if you are fixing an existing issue -->
   - [ ] Has associated issue:
   - [ ] Required feature flags:
   - [ ] Changes UI
   - [ ] Includes DB Migration (follow approval process in 
[SIP-59](https://github.com/apache/superset/issues/13351))
     - [ ] Migration is atomic, supports rollback & is backwards-compatible
     - [ ] Confirm DB migration upgrade and downgrade tested
     - [ ] Runtime estimates and downtime expectations provided
   - [ ] Introduces new feature or API
   - [ ] Removes existing feature or API
   


-- 
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