morrySnow opened a new pull request, #69103: URL: https://github.com/apache/doris/pull/69103
### What problem does this PR solve? Issue Number: N/A Related PR: https://github.com/apache/doris/pull/68154 Problem Summary: Post-bind INSERT constant folding could recompute nested field nullability while surrounding bound expressions kept their original layout, causing BE crashes for arrays of structs. Preserve bound signatures in normal and fast INSERT analysis. Place regression cases under the branch-4.2 nereids_p0 directory. ### Release note Fix BE crashes when inserting arrays of structs containing foldable nullable functions. ### Backport validation - Test: Unit Test: InsertUtilsTest; FE Checkstyle (0 violations). - Combined eight-backport validation: 283 tests across 13 classes, 0 failures/errors after correcting identity-cast assertions. This standalone backport has not had a separate unit-test run. - Regression tests were not run: no isolated branch-4.2 cluster was deployed. - Full build.sh --fe packaging was blocked by incomplete native third-party dependencies; the prescribed FE unit-test entry point compiled FE sources. - Behavior changed: Yes (post-bind INSERT rewrites preserve bound function signatures) - Does this need documentation: No (cherry picked from commit 3e878ed06764c53f6f1af3573a8de0b4fc8f5fa8) ### Scope This is an independent backport of #68154 onto branch-4.2. The branch contains one commit and does not include the other seven picks. The 283-test result above was obtained from the combined backport tree; this standalone branch has not had a separate unit-test run. ### Check List (For Author) - Test: - [x] Unit Test: 283 targeted tests passed on the combined backport tree. - [x] Manual test: standalone patch matches the validated pick; FE Checkstyle passed on the combined tree. - [ ] Regression test: no isolated branch-4.2 cluster was deployed. - Behavior changed: see the backport validation details above. - Does this need documentation: No. -- 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]
