Let's agree and fix the release date now so that we can all plan and prioritise accordingly. Improvements and bugs will always be there to fix and if we don't set a date we will keep deferring the release. The last major release (4.2.0) was a year ago so we have tons of new stuff that are just sitting on master.
How about cutting the next release on January 15th 2027? Do we have a release manager willing to drive it forward? Best, Stamatis On Mon, Nov 9, 2026 at 2:28 PM Denys Kuzmenko via dev <[email protected]> wrote: > > Hi Shohei, > > I'd estimate roughly 1–2 months for the minimal scope of HIVE-29733 required > for Hive 4.3.0, taking the holiday season into account. > > Regarding Iceberg performance, the remaining tickets I'd like to close are: > - HIVE-30108: Iceberg: cache DVs and V2 position deletes in the LLAP metadata > cache > - HIVE-30109: Iceberg: apply position deletes per batch > - HIVE-30112: Iceberg: V3 merge-on-read DML writes several DVs per data file > - HIVE-30113: Iceberg: V3 merge-on-read deletes ship every column to the DV > writer > > I agree that we should keep the 4.3.0 scope pragmatic and focus on the > essential items rather than trying to resolve every outstanding issue. > > Best regards, > Denys
