I assume the Iceberg Java already includes a full implementation of the Table Spec V3 features. Does the community have plans to switch the default table version from 2 to 3 for Iceberg tables created by Spark in the next release? This would help drive the adoption of new features such as Variant.
Thanks, Cheng Pan > On Aug 6, 2026, at 16:18, Alexandre Dutra <[email protected]> wrote: > > Hi Neelesh, > > If possible, I'd like to have this PR included: > > https://github.com/apache/iceberg/pull/15989 > > It's the fix for the path segment encoding issue in Iceberg REST. The > PR got one review already but isn't approved yet. > > Thanks, > Alex > > On Wed, Aug 5, 2026 at 10:37 PM Oğuzhan Ünlü <[email protected]> > wrote: >> >> Hi Neelesh, >> >> I'd like to get https://github.com/apache/iceberg/pull/16507 included in the >> milestone if possible. I previously asked for a review but didn't hear back. >> Not sure if that went to spam for some reason. >> >> Thanks, >> Oguzhan >> >> On Wed, Aug 5, 2026 at 11:03 PM Neelesh Salian <[email protected]> >> wrote: >>> >>> Hi folks, >>> >>> As mentioned during the community sync this morning, the release is on >>> track. >>> A few updates: >>> >>> I plan to cut the branch / RC on or after August 26, 2026 (after the >>> community sync that morning). I'll be working with Amogh to help with the >>> branching + artifacts. >>> There are still active items needing reviews. Please take a look at the >>> 1.12.0 milestone. >>> Calling out the Spark 4.2.0 PR: >>> https://github.com/apache/iceberg/pull/14984 - it needs more eyes and >>> review time to make this release. >>> I'll keep watching for blockers and bugs that should be part of the release >>> and surface them as needed, including any forward-porting to Spark 4.2. >>> >>> If you have a feature(s), fix(es), or breaking change(s) you want >>> considered for 1.12.0, please let me know. >>> >>> Thanks, >>> Neelesh >>> >>> On Fri, Jun 5, 2026 at 3:54 PM Steven Wu <[email protected]> wrote: >>>> >>>> If we develop good habit of regular releases, we normally won't need to >>>> hold the release train to get things in (except for critical security and >>>> correctness issues) as the next one is 2-3 months away. >>>> >>>> On Fri, Jun 5, 2026 at 3:42 PM Neelesh Salian <[email protected]> >>>> wrote: >>>>> >>>>> Hi folks, >>>>> >>>>> With 1.11.0 out the door, I want to open up the planning around 1.12.0. >>>>> As Steven noted on the dev list (thread for 1.11), 1.11.0 took roughly 8 >>>>> months from 1.10.0. This is longer than the 3-4 month cadence we have >>>>> previously discussed. >>>>> For 1.12.0 I'd like us to aim closer to that target. >>>>> >>>>> I'll be acting as the release manager for this release. Here are a few >>>>> notes to kick things off: >>>>> >>>>> Tentative release target: late August / early September 2026 (~3 months >>>>> from 1.11.0). >>>>> Curation: We'll use the June 24 community sync as the formal kickoff to >>>>> surface in-flight work and call out anything that should land in this >>>>> release. >>>>> Cadence reminder: If something doesn't make it in 1.12, the next one is >>>>> ~3 months out (1.13). >>>>> Mid-cycle check-in: I'll send a state-of-the-release update around >>>>> mid-July with what is in, what is in-flight, and what remains a blocker. >>>>> Tracking: The open issues and PRs targeting this release are tagged with >>>>> the Iceberg 1.12.0 milestone. I'll keep this milestone updated as things >>>>> land in the repo. >>>>> >>>>> If you have a feature, fix, or breaking change you want considered for >>>>> 1.12.0, please reply on this thread or flag it on the June 24 sync. >>>>> >>>>> Thanks, >>>>> Neelesh
