tree cbe55e53e8328aa097d2ec0c6d53220d41b06133
parent c74f584481d9bcefda7e8ac2a37feb2d61891fe4
author Stefan Bukorovic <stefan.bukorovic@databricks.com> 1714390936 +0800
committer Kent Yao <yao@apache.org> 1714390936 +0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQIzBAABCAAdFiEE124jufEbW/aGRhPE9wUYUKCvkE0FAmYvh5gACgkQ9wUYUKCv
 kE39AxAAyIb8+Gzi1DxrEsxcXTvszoVYnocxcvymUQscV848lBA0qbEdocMBVDKO
 X1iIHJLpFd/oNdzntKF2h86R8C7mnSGfnVZFGPL4DzbX7wiz4loQQYvRfQ6OjmVy
 Wl4Q++zIHKe2H9YJi3iTAI/0D8Whxo5Dl8DWMmGYNFePU1E1MAzAi5B4c6H0aLbf
 /BvZRHoCRfokf5X5zzi4OOJL9GIWg2fsw01+yIF7mXnZQbv/MHEwBeV+IVeNnEtc
 vpdEpiwqY8cW0PuzT78f9NCDJgjic7ogTnRyU8zB656jNCstCLIwoI+mE/5WokUb
 K+LmcOJIFxMJoNaFusMldM4xOQH0wOQJK6bufjL/+gvIl1oSN9NdxZSe2FB4Zlsn
 lVq2anu3BQ9EJRpQqkb0RAmnJ0iJ/D/z2uf9la1wOqmsuZw1WiiOO2G3Rw8rhdk8
 05OIE1ynpQyvDAXEK3EjSynjHblSXHz6jhzmgqFuGbmPVMNV6wP+Kwk0axuM4NeQ
 N1qGEAX1RHKWj9opKKssPjLJ6/JF4y7XbeaxET0+QNn47vBbhqbYq+PmbIQ3OKek
 kwysdgVNc0Hh8QCIEwYoF8LWTk0edyT/se62hFClSdKzlVT6JcvnWGiljxxoYMtx
 V/Fos8HxzjydwIZLNsZXKg+hkt2q2AF1w8Wlx2Vncgl8d6sKBnM=
 =oKtM
 -----END PGP SIGNATURE-----

[SPARK-47994][SQL] Fix bug with CASE WHEN column filter push down in SQLServer

### What changes were proposed in this pull request?

In this PR I propose a change in QueryBuilder for SQLServer. This change modifies push down of predicate that contains a column that is generated with a CASE WHEN construct, so that we add simple ` = 1` comparison to this query, making it work on SQLServer.

### Why are the changes needed?

SQLServer does not support 0 or 1 as a boolean values. There are certain situations where spark optimizer rewrites filters that contain CASE WHEN columns in a way that adds 1 or 0 as a boolean values, which fails on SQLServer side with an error "An expression of non-boolean type specified in a context where a condition is expected". With these changes, we modify pushing this filters down, and error is no longer present.

### Does this PR introduce _any_ user-facing change?

No

### How was this patch tested?
A new test case is added, which fails without these changes.

### Was this patch authored or co-authored using generative AI tooling?
No

Closes #46231 from stefanbuk-db/SQLServer_case_when_bugfix.

Authored-by: Stefan Bukorovic <stefan.bukorovic@databricks.com>
Signed-off-by: Kent Yao <yao@apache.org>