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?
Yes. We can make changes to v3 until the community votes to adopt and close
the version to any new forward-breaking changes. That vote isn’t tied t
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 main
Hi Anton,
AFAIR, when we discussed the 1.7.0 release, we agreed about the "best
effort" regarding V3. Regarding the major PRs you are mentioning, we
can always include in 1.7.1 and following.
I think we can still wait a few days before the freeze, but not weeks.
I think we should move forward on 1
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
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é
Keep up coming :) I did a pass on Prashant's as well
On Wed, Oct 23, 2024 at 12:47 AM Jean-Baptiste Onofré
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,
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 wrote:
>
> Hi Russell,
>
> I recently stumbled across an issue in Iceberg Kafka-Connect which shows up
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
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
That's still my current plan
On Mon, Oct 21, 2024 at 10:52 AM Rodrigo Meneses 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é
> wrote:
>
>> Hi Ru
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é wrote:
> Hi Russ
>
> As discussed during the community sync, I agree with this plan.
>
> In the meantime (as you saw o
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 Russe
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 jus
12 matches
Mail list logo
