Hi Quanlong, Thank you for your efforts, I think the key to whether release a 4.1.1 branch is how many break changes from 4.1.0 to 4.2.0, and how important the ratio of user 4.1.0. For the second question, maybe we can create a questionnaire.
Thanks, Xiang Yang At 2022-08-01 17:41:12, "Quanlong Huang" <huangquanl...@gmail.com> wrote: >Hi team, > >Impala 4.1.0 was released in June. There are a bunch of bug fixes after >that. It'd be nice to release 4.1.1 with them. > >I just tried cleanly cherrypick as more fixes as possible to branch-4.1.0. >Here are what I got: >https://github.com/stiga-huang/impala/commits/branch-4.1.1 > >There are some fixes that have cherrypick conflicts: > >1a1536bd1d0162a168877a6f33dd75f9544a82f3 IMPALA-11346: Migrated partitioned >Iceberg tables might return ERROR when WHERE condition is used on partition >column >4174ff5ea6a1b413a6218d26bbb7cf20809623cd IMPALA-11320: SHOW PARTITIONS on >Iceberg table doesn't list the partitions >8d034a2f7cd2f68714e83b28335b3baf18823d7c IMPALA-11034: Resolve schema of >old data files in migrated Iceberg tables >e1fea843ea2654d3acfef152e1a073dbef91aa9c IMPALA-11433: Remove misleading >bucketing info from DESCRIBE FORMATTED output for Iceberg tables >1d16367afb1e520bae5992c1e6c92b4fb41d2655 IMPALA-10871 (part 2): Apache Hive >3: fixes for dataset loading > >I haven't merged them yet. > >Do you think it makes sense to create a 4.1.1 branch? So we can prepare the >4.1.1 release and do code review for resolving such cherrypick conflicts. > >Thanks, >Quanlong
