Hi Jiunn-Yang,
Thanks for the KIP!
I agree that this oddity should be fixed. It's a bit of a funny case, KIP-wise,
in that the API signature itself isn't changing, but the documentation and
behavior are.
Some questions:
KT1: The KIP specifically calls out "The scenarios that will be impacted"
Ritika Reddy created KAFKA-19003:
Summary: Add force-terminate command to kafka-transactions CLI
Key: KAFKA-19003
URL: https://issues.apache.org/jira/browse/KAFKA-19003
Project: Kafka
Issue
David Arthur created KAFKA-19000:
Summary: Flaky test report should use absolute time for links
Key: KAFKA-19000
URL: https://issues.apache.org/jira/browse/KAFKA-19000
Project: Kafka
Issue Ty
cmccabe merged PR #667:
URL: https://github.com/apache/kafka-site/pull/667
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.
[
https://issues.apache.org/jira/browse/KAFKA-18808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-18808.
Resolution: Fixed
> add test to ensure the name= is not equal to default quota
> -
Chia-Ping Tsai created KAFKA-19002:
--
Summary: Rewrite ListOffsetsIntegrationTest and move it to
clients-integration-test
Key: KAFKA-19002
URL: https://issues.apache.org/jira/browse/KAFKA-19002
Projec
hi PoAn
Considering that the Endpoint API is now considered stable, would you please
create a minor patch to remove the @InterfaceStability.Evolving annotation?
This annotation was introduced in version 2.4.0 (see
https://github.com/apache/kafka/commit/364794866f82d2d99f7a610d699478d5055688f0),
Thanks Ismail,
I've opened https://github.com/apache/kafka/pull/19221 just to get any test
failures out of the way in case it is decided to do this backport.
I'm hoping people will weigh in with their concerns in this thread if they
don't like the idea of backporting this change.
Den man. 17. ma
[
https://issues.apache.org/jira/browse/KAFKA-17565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-17565.
Resolution: Fixed
> Move MetadataCache interface to metadata module
>
[
https://issues.apache.org/jira/browse/KAFKA-17171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-17171.
Fix Version/s: 4.1.0
Resolution: Fixed
> Add test cases for `STATIC_BROKER_CONFIG`i
Lucas Brutschy created KAFKA-19001:
--
Summary: Use streams group-level configurations in heartbeat
Key: KAFKA-19001
URL: https://issues.apache.org/jira/browse/KAFKA-19001
Project: Kafka
Issue
Hi Stig,
Kafka 4.0 is likely to be released in a day or two. Even so, I think it
makes sense to revive the backporting thread given the lack of workaround
for Java 24.
Ismael
On Mon, Mar 17, 2025 at 7:44 AM Stig Rohde Døssing
wrote:
> Hi,
>
> Some months ago, a reflective shim was added in
> h
Hi,
> The evolving annotation was left by mistake given that
>> these
> classes have been there for a long time by now.
I misunderstood evolving annotation, so I tried to change listenerName from
Optional to String at the first version. Change to deprecate
listenerName
in 4.1. I will inc
Hi,
Some months ago, a reflective shim was added in
https://issues.apache.org/jira/browse/KAFKA-17078, in order to support
running Kafka with SASL on JDKs that no longer support the security
manager.
This shim was added only to Kafka 4.0, but backporting was discussed in
https://lists.apache.org/
Hi,
This approach should work. I think `name` is a bit too generic. Perhaps
`listener` would be a better option for the non deprecated method name.
Ismael
On Mon, Mar 17, 2025 at 5:42 AM Chia-Ping Tsai wrote:
> Maybe we can add new method `name()` same to `RaftVoterEndpoint#name`.
>
> in 4.x:
Hi Juma and Chia-Ping,
Thanks for the review and suggestions.
chia_q0: I change KIP to deprecate listenerName function in 4.1 and replace it
with name function.
In 5.0, the deprecated function listerName will be removed.
chia_q1: Add RaftVoterEndpoint and StreamsGroupMemberDescription#Endpoint
Hi all,
Thanks for all the votes. We already have 4 binding votes. I am planning to
close the vote in 24 hours.
Best,
David
On Sun, Mar 16, 2025 at 12:31 PM Luke Chen wrote:
> Hi David,
>
> The system tests link works for me now. Thanks.
> The failed tests are the same as RC3, so it looks good
Maybe we can add new method `name()` same to `RaftVoterEndpoint#name`.
in 4.x:
1) add `org.apache.kafka.common.Endpoint#name()`
2) deprecate `org.apache.kafka.common.Endpoint#listenerName()`
3) replace `org.apache.kafka.common.Endpoint` by
`org.apache.kafka.network.Endpoint`
in 5.x
1) remove
Hi David,
we ran all the automated regression pipelines by using the Kafka 4.0.0 RC4
binaries within the next planned Strimzi 0.46.0 release (Kafka on
Kubernetes).
Everything seems to be fine so this RC4 looks good to me.
+1 non binding
Thanks for running the release.
Cheers,
Paolo
On Fri, 14 M
To be clear, that's not the only issue. There is no way to make a
compatible change in signature like the one proposed by 5.0. Two major
releases would be required. And we also need a non deprecated method to be
used in the meantime.
Ismael
On Mon, Mar 17, 2025, 12:41 AM Chia-Ping Tsai wrote:
>
hi PoAn,
chia_q0:
To prevent potential misinterpretations, could you please explicitly list
the features that will be deprecated and added in Kafka 4.x, and those that
will be removed in Kafka 5.x? Without this clarification, readers might
mistakenly assume that breaking changes are planned for Ka
21 matches
Mail list logo
