Folks, It's been about 3 months since our last release and there have been a good number of bug fixes, features added and performance improvements since then.
I propose that we have a 2.12.0 release soon and a 3.0 release in parallel. I, as a PMC of Apache Impala volunteer to mange both these releases. Why have 2 releases in parallel? We've been maintaining 2 branches in parallel for a while now. A 2.x branch which works with Hadoop 2.0 and friends, and a master branch, which now works with Hadoop 3.0 and friends. We've also made sure to not push any incompatible changes into our 2.x branch, but only to the master branch, and we have a good number of these incompatible changes on master now that justifies having a 3.0 release. There have been 351 commits on master since the last release, Apache Impala 2.11.0. I've gone through them and outlined the commits that are either considered breaking changes or support a breaking change: IMPALA-4277: Switch to using Hadoop 3 and friends by default. IMPALA-6510: [DOCS] Remove refresh_after_connect IMPALA-6647: Add CREATE fine-grained privilege IMPALA-6230, IMPALA-6468: Fix the output type of round() and related fns IMPALA-4277: Support multiple versions of Hadoop ecosystem IMPALA-6415: [DOCS] fix invalid <ph conref> IMPALA-6643: Add REFRESH fine-grained privilege IMPALA-5191, IMPALA-6415: [DOCS] Document breaking change of alias and ordinal substitution IMPALA-3916: [DOCS] Reserved keywords updated for Impala 3.0 IMPALA-6240: [DOCS] Document PARQUET_ARRAY_RESOLUTION query option [DOCS] Removed the obsolete Llama options files IMPALA-6077: remove Parquet BIT_PACKED def level support IMPALA-3271: organise and warn on removed startup flags IMPALA-5037: Default PARQUET_ARRAY_RESOLUTION=THREE_LEVEL IMPALA-5293: Turn insert clustering on by default IMPALA-4924 addendum: Change result type to decimal in a TPCH query IMPALA-3916: Reserve SQL:2016 reserved words (Disabled on 2.x with IMPALA-3916: Change reserved_words_version to 2.11.0) IMPALA-4319: remove some deprecated query options IMPALA-4924: Enable Decimal V2 by default IMPALA-5191: Standardize column alias behavior IMPALA-3998: Remove refresh_after_connect option from shell The 3.0 release would come off the master branch and the 2.12.0 release would come off the 2.x branch. Please speak up and let the community know if anyone has any objections to this. P.S: This is not a VOTE thread but only a DISCUSS thread. Thanks, Sailesh
