On Thu, May 29, 2025, at 08:37, José Armando García Sancio wrote:
> Hi Colin,
>
> On Tue, May 27, 2025 at 8:57 PM Colin McCabe wrote:
>> My argument was that it would be unlikely that all three of these things
>> would be true. One reason why I think this is that 3.7-IV3 is a pretty old
>> MV at
Hi Colin,
On Tue, May 27, 2025 at 8:57 PM Colin McCabe wrote:
> My argument was that it would be unlikely that all three of these things
> would be true. One reason why I think this is that 3.7-IV3 is a pretty old MV
> at this point anyway.
Then why not enforce that in the KIP and code? You ar
On Tue, May 27, 2025, at 09:28, José Armando García Sancio wrote:
> Hi Colin,
>
> On Fri, May 2, 2025 at 6:52 PM Colin McCabe wrote:
>>
>> On Fri, May 2, 2025, at 09:54, José Armando García Sancio wrote:
>> That seems pretty clear? It's also already implemented (although not used
>> since we don'
Hi Colin,
On Fri, May 2, 2025 at 6:52 PM Colin McCabe wrote:
>
> On Fri, May 2, 2025, at 09:54, José Armando García Sancio wrote:
> That seems pretty clear? It's also already implemented (although not used
> since we don't have any inter-dependent features yet).
I see. This is mentioned in the
On Fri, May 2, 2025, at 09:54, José Armando García Sancio wrote:
> Hi Colin,
>
> On Fri, Apr 25, 2025 at 5:42 PM Colin McCabe wrote:
>> > The "initiating the downgrade" section states "It will also check that
>> > the requested metadata version is compatible with all the other
>> > KIP-584 feature
Hi Colin,
On Fri, Apr 25, 2025 at 5:42 PM Colin McCabe wrote:
> > The "initiating the downgrade" section states "It will also check that
> > the requested metadata version is compatible with all the other
> > KIP-584 features that are enabled." What do you mean by this?
>
> So, in Kafka version 4
On Fri, Apr 25, 2025, at 16:11, Matthias J. Sax wrote:
> Hey Colin,
>
> I want to follow up to Andrew questions and your replies.
>
> First, yes both KIP-932 and KIP-1071 are going to use "Features".
>
> - https://github.com/apache/kafka/pull/19293
> - https://github.com/apache/kafka/pull/19509
Hey Colin,
I want to follow up to Andrew questions and your replies.
First, yes both KIP-932 and KIP-1071 are going to use "Features".
- https://github.com/apache/kafka/pull/19293
- https://github.com/apache/kafka/pull/19509
Don't think it's mentioned on the KIPs (at least not for KIP-1071).
Hi Colin,
Thanks for the KIP. I have a few questions and comments.
The "initiating the downgrade" section states "It will also check that
the requested metadata version is compatible with all the other
KIP-584 features that are enabled." What do you mean by this?
In the same section, you have "I
On Fri, Apr 25, 2025, at 14:26, José Armando García Sancio wrote:
> Hi Colin,
>
> Thanks for the KIP. I have a few questions and comments.
>
> The "initiating the downgrade" section states "It will also check that
> the requested metadata version is compatible with all the other
> KIP-584 features
Hi Jun,
The controller knows if there is metadata lost when it tries to write a new
metadata image with the update MV. When the handleLoss callback is triggered,
that indicates that metadata is lost.
isBackwardsCompatible is not needed and will not be implemented for MV
best,
Colin
On Tue, Ap
Hi, Colin,
Thanks for the KIP.
During downgrade, how does the controller know whether there is metadata
loss in the process? Do we still plan to implement the
isBackwardsCompatible flag in MV as described in KIP-778?
Jun
On Mon, Apr 7, 2025 at 3:05 PM Colin McCabe wrote:
> Hi all,
>
> I poste
ic metadata version. However, for things
like the group coordinator, it wouldn't really make sense to tie to a
metadata.version, since it's so separate.
Hope this helps.
best,
Colin
>
> Thanks,
> Andrew
>
> ____________
> From: Colin McC
5 20:46
To: dev@kafka.apache.org
Subject: Re: KIP-1155: Metadata Version Downgrades [DISCUSS]
On Tue, Apr 8, 2025, at 09:55, Justine Olshan wrote:
> Hey PoAn,
>
> Just wanted to make a clarification. TV2 doesn't need to be downgraded if
> the MV is lower than the bootstrap MV for th
Hi all,
I posted a new KIP about support metadata.version downgrades. Take a look here:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-1155%3A+Metadata+Version+Downgrades
thanks,
Colin
On Tue, Apr 8, 2025, at 09:55, Justine Olshan wrote:
> Hey PoAn,
>
> Just wanted to make a clarification. TV2 doesn't need to be downgraded if
> the MV is lower than the bootstrap MV for the TV.
> The bootstrap MV is only used when the cluster is created to get the
> default feature versions. As lo
On Tue, Apr 8, 2025, at 01:58, PoAn Yang wrote:
> Hi Colin,
>
> Thanks for the KIP. It’s good to give users more flexibility to
> downgrade metadata.version.
>
> PY1: Each feature has bootstrapMetadataVersion. For example, TV_2 is
> IBP_4_0_IV2.
> Assume that a cluster uses TV_2 and metadata.vers
Hey PoAn,
Just wanted to make a clarification. TV2 doesn't need to be downgraded if
the MV is lower than the bootstrap MV for the TV.
The bootstrap MV is only used when the cluster is created to get the
default feature versions. As long as the TV version is a production version
for the Kafka relea
Hi Colin,
Thanks for the KIP. It’s good to give users more flexibility to downgrade
metadata.version.
PY1: Each feature has bootstrapMetadataVersion. For example, TV_2 is
IBP_4_0_IV2.
Assume that a cluster uses TV_2 and metadata.version 4.0-IV2. If a user
downgrades
metadata.version to 3.9-IV0
19 matches
Mail list logo
