Hi all, Impala 4.1.1 was released in Oct. 2022. There are several bug fixes that would be nice to be backported, e.g.
d3ece4433 IMPALA-11857: Connect join build fragment to join in graphical plan ff7b5db60 IMPALA-11081: Fix incorrect results in partition key scan 32536ba25 IMPALA-11845: (Addendum) Don't specify db name in the new struct tests 0c1bd9eff IMPALA-11845: Fix incorrect check of struct STAR path in resolvePathWithMasking b0009db40 IMPALA-11843: Fix IndexOutOfBoundsException in analytic limit pushdown 11068d9ae IMPALA-11811: Avoid storing unregistered predicate objects in a Map b816b6e39 IMPALA-11753: CatalogD OOMkilled due to natively allocated memory 6838e988a IMPALA-11696: Fix incorrect warnings of ignoring delimiters on text/sequence tables 3c9d23a23 IMPALA-11707: Fix global runtime IN-list filter of numeric types are AlwaysFalse 367378438 IMPALA-11744: Table mask view should preserve the original column order in Hive f8819ac7c IMPALA-11751: (Addendum) fix test for Ozone bd9f44838 IMPALA-11751: Template tuple of Avro header should be transferred to ScanRangeSharedState 77d80aeda IMPALA-11812: Deduplicate column schema in hmsPartitions 64efb7695 IMPALA-11779: Fix crash in TopNNode due to slots in null type Though we have released 4.2.0 in Dec. 2022, the 4.1 branch can be considered as a stable release since it's a better target for 3.x users to upgrade to 4.x, e.g. Impala 4.1 depends on kudu 1.16, while Impala 4.2 depends on a snapshot version of Kudu. I propose that we do a maintenance release for 4.1.2. What do you think? If there are no objections, I volunteer to be the release manager of Impala 4.1.2. Thanks, Quanlong
