hello-stephen opened a new pull request, #68798: URL: https://github.com/apache/doris/pull/68798
### What problem does this PR solve? Backport #68308 / #68401 to branch-4.1. The repair is present on branch-4.1.4, but branch-4.1 at c8c0ddca4d4d452bcb236f2499c5fed9a3c68780 still has the same three unnormalized OR paths as 4.1.5-rc01 (7fda449b7afb09c266ce2c4fc738a4d5e46fc458). A nullable Boolean can contain an arbitrary hidden byte. When the other operand makes OR non-null, preserving the bitwise result can expose a value other than 0 or 1. Release regression reproduced incorrect Boolean grouping on the original candidate in both LOCAL and S3 modes. This is an exact backport of fc344110d103312a6bfafb55e936b76f26177b8e, preserving its author and all five changed files: normalize FunctionOr and both compound OR paths, add three BE unit tests, and include the original regression suite and unchanged golden output. No unrelated NULL/CASE implementation changes are included. ### Release note Fix noncanonical logical OR results involving hidden NULL payloads. ### Check List (For Author) - Validation: patch applies cleanly to the stated branch-4.1 base; all five resulting files are byte-identical to the original fixed commit; git diff --check passes. - Runtime validation: this new backport has not run BE unit tests or live regression yet. Required validation is FunctionsLogicalTest.* and test_json_extract_bool_null_payload in LOCAL/S3, with both short-circuit settings, against a binary built from this PR's exact SHA. - The existing candidate failure remains a release blocker. This PR does not replace the candidate artifact or establish a passing release result. - Duplicate check: currently open branch-4.1 PR file lists and matching repair references were checked; no equivalent open backport was found. -- 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]
