Hi Luke,
Thanks for the work on this release. I would have liked to see this PR
included, but I guess the train was missed for this one. Is it possible to
get some attention to this for the next release?
https://github.com/apache/kafka/pull/17930
Thanks,
Den ons 9 apr. 2025 kl 14:17 skrev Luke
Hi all,
Thanks Juha for bringing this discussion here. To everyone else, I am
Juha's colleague at Aiven and am currently working on introducing the kind
of tooling discussed in this thread, to be used in worst case scenarios. I
have a proof of concept working. The various input and concerns raised
for any feedback,
Anton
--
[image: Aiven] <https://www.aiven.io/>
*Anton Agestam* (he/him or they/them)
Software Engineer, *Aiven*
anton.ages...@aiven.io | +46 704 486 289
aiven.io <https://www.aiven.io/> |
<https://www.facebook.com/aivencloud>
<https://www.linkedin.com/company/aiven/><https://twitter.com/aiven_io>
Anton Agestam created KAFKA-18061:
-
Summary: AddRaftVoter responds with error message "NONE" instead
of null
Key: KAFKA-18061
URL: https://issues.apache.org/jira/browse/KAFKA-18061
Proj
Hello,
I also think this sounds like a reasonable suggestion, also given that 3.9
was the first version to make KRaft feature complete, which means it's the
first version to bring production readiness for KRaft, in many contexts.
+1 from me.
BR,
Den tors 21 nov. 2024 kl 10:51 skrev Josep Prat :
m && git checkout -b scratch
84caaa6e9da06435411510a81fa321d4f99c351f
Is there something broken in the repository?
[image: Skärmavbild 2024-11-14 kl. 17.01.24.png]
--
[image: Aiven] <https://www.aiven.io/>
*Anton Agestam* (he/him or they/them)
Software Engineer, *Aiven*
anton.ages
Oh sorry for the noise all, I missed a couple subsequent responses that
already addressed this.
Den tis 12 nov. 2024 kl 16:05 skrev Anton Agestam :
> Hi Matthias,
>
> Thanks for your input and for pointing that out.
>
> It at least is missing from this wiki page, and so is a
ve that we do not have the
> people to
> >> do that, so let's at least collect the information in some reasonable
> form.
> >>
> >
> > Many changes involve multiple PRs. I think documentation is no different
> than any other aspect of a feature or change
hanging the protocol. I don't think it necessary needs to be done before
> the change itself, but it should be done so that the release that includes
> the protocol changes also includes their docs...
>
> best,
> Colin
>
>
> On Sat, Oct 26, 2024, at 10:53, Anton Agestam wro
ose are very bad default
values. Similarly, for timestamp fields the resulting value will be epoch,
which extremely rarely is a useful default.
Cheers,
Anton
Den mån 28 okt. 2024 kl 17:02 skrev Colin McCabe :
> On Sun, Oct 27, 2024, at 01:44, Anton Agestam wrote:
> > Colin
> >
> &g
is on track.
>
> Best,
> Chia-Ping
>
> [0]
> https://github.com/apache/kafka/blob/3.8/clients/src/main/resources/common/message/FetchSnapshotResponse.json#L43
> [1]
> https://github.com/apache/kafka/blob/3.8/group-coordinator/src/main/resources/common/message/ConsumerGroupMemberMet
ements over time, having that in place would be a
motivation for me to contribute further to the documentation of the wire
protocol.
Cheers,
Anton
Den mån 28 okt. 2024 kl 17:02 skrev Colin McCabe :
> On Sun, Oct 27, 2024, at 01:44, Anton Agestam wrote:
> > Colin
> >
> > I have p
-1, refer to comments on the RC 2 thread.
Den sön 27 okt. 2024 kl 02:51 skrev Colin McCabe :
> This is the RC5 candidate for the release of Apache Kafka 3.9.0.
>
> - This is a major release, the final one in the 3.x line. (There may of
> course be other minor releases in this line, such as 3.9.1.
this should change.
>
> There simply isn't any reason to change the current tagged fields
> behavior. And even if we wanted to, it would require a KIP, whereas 3.9 is
> past KIP freeze (along with feature freeze, code freeze, and every other
> freeze.)
>
> best,
> Colin
stment of time to improve documentation of the current state. For the
continued success of Kafka this is highly important because it is what
enables a thriving ecosystem.
- Have there been something similar discussed previously?
- What do you all think of this proposal?
BR,
Anton
--
[image: Aiven] <h
inion, though, that we might have to agree to
> disagree about...
>
> best,
> Colin
>
>
> On Fri, Oct 25, 2024, at 01:37, Anton Agestam wrote:
> > Hi again Colin,
> >
> >> The implicit defaults have been documented for a long time
> >
> > Yes, if
y to both tagged and untagged fields. The main difference is
> that untagged fields are always present except in older versions, whereas
> tagged fields may not be present even in the most recent version.
>
> Perhaps there is something we could do to improve these docs? Or somehow
>
ug, you just failed to
> > account for implicit defaults in your protocol code. That is, 0 is the
> > default of numeric fields if no other default is specified, etc.
> >
> > best,
> > Colin
> >
> > On Mon, Oct 21, 2024, at 08:07, Anton Agestam wrote:
> >
Hi everyone,
I have found a protocol serialization bug that surfaces only with one of
the entities introduced for KIP-853 (UpdateRaftVoterResponse).
Due to the irreversible implications this might have once merged, I'd argue
that this needs to be considered a release blocker.
https://issues.apac
Anton Agestam created KAFKA-17845:
-
Summary: UpdateRaftVoterResponse has incorrect default value
fallbacks
Key: KAFKA-17845
URL: https://issues.apache.org/jira/browse/KAFKA-17845
Project: Kafka
age: Aiven] <https://www.aiven.io/>
*Anton Agestam* (he/him or they/them)
Software Engineer, *Aiven*
anton.ages...@aiven.io | +46 704 486 289
aiven.io <https://www.aiven.io/> |
<https://www.facebook.com/aivencloud>
<https://www.linkedin.com/company/aiven/><https://twitter.com/aiven_io>
+1 from me.
Den fre 5 jan. 2024 kl 10:33 skrev Josep Prat :
> Hi all,
>
> I'd like to start a vote on KIP-1012:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1012%3A+The+need+for+a+Kafka+3.8.x+release
>
> Discussion thread is here:
> https://lists.apache.org/thread/kvdp2gmq5gd9txkvxh5
Sorry, the underscore was meant to refer to the
https://github.com/apache/kafka/tree/trunk/clients/src/main/resources/common/message
directory in the previous message.
Den fre 24 nov. 2023 kl 14:30 skrev Anton Agestam :
> Hi Ismael,
>
> This looks like a healthy KIP for Kafka 👍
&
Hi Ismael,
This looks like a healthy KIP for Kafka 👍
As the implementer of a Kafka Protocol library for Python, Aiven-Open/kio
[1], I'm curious how this change will affect the library.
We generate entities for the full protocol by introspecting the JSON schema
definitions under _. How will the K
;just one more feature" before they
> >> migrate.
> >> >>
> >> >> best,
> >> >> Colin
> >> >>
> >> >>
> >> >> On Mon, Nov 20, 2023, at 04:15, Josep Prat wrote:
> >> >> > Hi all,
&g
Anton Agestam created KAFKA-15869:
-
Summary: Document semantics of nullable nested API entities
Key: KAFKA-15869
URL: https://issues.apache.org/jira/browse/KAFKA-15869
Project: Kafka
Issue
tures we could do, we
> can't really block the release for any one feature.
>
> To circle back to KIP-853, I think it stands a good chance of making it
> into AK 4.0. Jose, Alyssa, and some other people have worked on it. It
> definitely won't make it into 3.7, since we
Hi Luke,
We have been looking into what switching from ZK to KRaft will mean for
Aiven.
We heavily depend on an “immutable infrastructure” model for deployments.
This means that, when we perform upgrades, we introduce new nodes to our
clusters, scale the cluster up to incorporate the new nodes, a
Hi Luke,
We have been looking into what switching from ZK to KRaft will mean for
Aiven.
We heavily depend on an “immutable infrastructure” model for deployments.
This means that, when we perform upgrades, we introduce new nodes to our
clusters, scale the cluster up to incorporate the new nodes, a
29 matches
Mail list logo
