Do I recall our agreement that any V3 spec changes that will be released bear no compatibility guarantees until we close V3 and vote on it as a whole?
There are a few major PRs unrelated to V3 that are close but unlikely to be merged by the end of this week: - Amogh and I were working on sync maintenance for V2 position deletes in core and Spark. The final PRs are being reviewed but we are re-evaluating if the broadcast approach is the way to go. We may need to revert some previously merged parts in 1.7 to avoid breaking the API in 1.8. - Ajantha wrote a utility for computing partition stats, which is already in main. There is an open PR for writers but I think we may need to switch to "internal" writers, which will need a bit of time to iterate. - Wing Yew Poon has a PR to support V2 tables in ChangelogScan but we need to optimize the computation and make it incremental. There is no need to block 1.7 for these changes (except any potential reverts for sync maintenance), but we may want to do 1.8 some time in November. - Anton ср, 23 жовт. 2024 р. о 17:28 Manu Zhang <owenzhang1...@gmail.com> пише: > Can we also include https://github.com/apache/iceberg/pull/11157? Much > appreciated if I can get more eyes on it. > > Thanks, > Manu > > On Wed, Oct 23, 2024 at 11:03 PM Russell Spitzer < > russell.spit...@gmail.com> wrote: > >> Keep up coming :) I did a pass on Prashant's as well >> >> On Wed, Oct 23, 2024 at 12:47 AM Jean-Baptiste Onofré <j...@nanthrax.net> >> wrote: >> >>> Hi Prashant >>> >>> Thanks for the heads up. We still have time to review and include in >>> the release. >>> >>> I will do a pass on your PR. >>> >>> Thanks ! >>> Regards >>> JB >>> >>> On Tue, Oct 22, 2024 at 9:29 PM Prashant Singh <prashant010...@gmail.com> >>> wrote: >>> > >>> > Hi Russell, >>> > >>> > I recently stumbled across an issue in Iceberg Kafka-Connect which >>> shows up when we are using UUID / FixedType, which leads to failure when we >>> are actually writing the files, so makes it kinda unusable when we are >>> using these data-types. >>> > I have a fix out for it already : >>> https://github.com/apache/iceberg/pull/11346/files . Would request you >>> include this as well into 1.7.0. >>> > >>> > Regards, >>> > Prashant Singh >>> > >>> > On Mon, Oct 21, 2024 at 9:13 AM Wing Yew Poon >>> <wyp...@cloudera.com.invalid> wrote: >>> >> >>> >> Hi Russell, >>> >> There is a data correctness issue ( >>> https://github.com/apache/iceberg/issues/11221) that I have a fix for ( >>> https://github.com/apache/iceberg/pull/11247). This is a serious issue, >>> and I'd like to see the fix go into 1.7.0. >>> >> Eduard has already approved the PR, but he asked if you or Amogh >>> would take a look as well. >>> >> Thanks, >>> >> Wing Yew >>> >> >>> >> >>> >> On Mon, Oct 21, 2024 at 8:56 AM Russell Spitzer < >>> russell.spit...@gmail.com> wrote: >>> >>> >>> >>> That's still my current plan >>> >>> >>> >>> On Mon, Oct 21, 2024 at 10:52 AM Rodrigo Meneses <rmene...@gmail.com> >>> wrote: >>> >>>> >>> >>>> Hi, team. Are we still targeting to cut off on October 25th and >>> release by Oct 31the, for the 1.7.0 release? >>> >>>> Thanks >>> >>>> -Rodrigo >>> >>>> >>> >>>> >>> >>>> On Thu, Oct 3, 2024 at 9:03 PM Jean-Baptiste Onofré < >>> j...@nanthrax.net> wrote: >>> >>>>> >>> >>>>> Hi Russ >>> >>>>> >>> >>>>> As discussed during the community sync, I agree with this plan. >>> >>>>> >>> >>>>> In the meantime (as you saw on row lineage doc), I'm working on V3 >>> >>>>> spec proposals (reviews, PRs, ...). >>> >>>>> >>> >>>>> If needed, I can be volunteer as release manager for the 1.7.0 >>> release. >>> >>>>> >>> >>>>> Regards >>> >>>>> JB >>> >>>>> >>> >>>>> On Fri, Oct 4, 2024 at 5:55 AM Russell Spitzer >>> >>>>> <russell.spit...@gmail.com> wrote: >>> >>>>> > >>> >>>>> > Hi y'all! >>> >>>>> > >>> >>>>> > As discussed at the community sync on Wednesday, October has >>> begun and we are beginning to flesh out the 1.7.0 release as well as the V3 >>> Table Spec. Since we are a little worried that we won't have all of the >>> Spec items we want by the end of October, we discussed that we may want to >>> just do a release with what we have at the end of the month. >>> >>>>> > >>> >>>>> > It was noted that we have a lot of exciting things already in >>> and we may be able to get just the beginning of V3 support as well. >>> >>>>> > >>> >>>>> > To that end it was proposed that we do the next Iceberg release >>> at the end of the month (Oct 31st) , and have the cutoff a week before (Oct >>> 25th). Does anyone have objections or statements of support for this plan? >>> >>>>> > >>> >>>>> > With this in mind please also start marking any remaining PR's >>> or Issues that you have with 1.7.0 so we can prioritize them for the cutoff >>> date. >>> >>>>> > >>> >>>>> > >>> >>>>> > Thanks everyone for your time, >>> >>>>> > Russ >>> >>
