Hi all,
As part of making these changes and testing the clients mentioned in the
KIP, we identified a number of adjustments required to satisfy the premise
that released versions of the clients mentioned in the KIP would work with
Apache Kafka 4.0:
https://cwiki.apache.org/confluence/pages/diffpa
Ismael Juma created KAFKA-18663:
---
Summary: Metadata v0-v3 should be undeprecated
Key: KAFKA-18663
URL: https://issues.apache.org/jira/browse/KAFKA-18663
Project: Kafka
Issue Type: Sub-task
> The ZooKeeper project fixed this bug in ZooKeeper
> 3.9.3 but it is unlikely that we will upgrade the ZooKeeper version
> for Kafka 3.9.x.
Our decision on upgrading dependencies likely hinges on how we approach Kafka
version 3.9.x. For branches in maintenance mode, it's generally advisable to
[
https://issues.apache.org/jira/browse/KAFKA-18648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-18648.
-
Resolution: Fixed
> kafka-python requires metadata request version 0
> -
Interesting thoughts. So maybe we could go with `BatchWindows` as a
name? Again, only spit-balling...
If we really put "(micro-)batching" in the center of this idea, I think
both count-based and time-based (and time could actually be either
stream-time or wall-clock-time), or any combination o
Justine Olshan created KAFKA-18662:
--
Summary: Return CONCURRENT_TRANSACTIONS on produce request for TV2
Key: KAFKA-18662
URL: https://issues.apache.org/jira/browse/KAFKA-18662
Project: Kafka
Hi all,
I am not sure if this was discussed before but what is our plan for
jira (bugs) that are specific to the implementation of Kafka that is
specific to the ZooKeeper implementation?
It would be nice to easily identify all such jiras. Should we tag all
such jiras with the zookeeper label?
Sh
Thanks for the feedback Lucas and Bruno!
L0. "Given the motivation section, it sounds we actually want something
that I'd call "batching" rather than "windowing"."
You are right here, and I think ultimately introducing more flexible and
controlled micro-batching will be useful for Kafka Streams,
[
https://issues.apache.org/jira/browse/KAFKA-18661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan resolved KAFKA-18661.
Resolution: Duplicate
Jira was spinning and created this twice.
> Transactions Version 2
Justine Olshan created KAFKA-18660:
--
Summary: Transactions Version 2 doesn't handle epoch overflow
correctly
Key: KAFKA-18660
URL: https://issues.apache.org/jira/browse/KAFKA-18660
Project: Kafka
Justine Olshan created KAFKA-18661:
--
Summary: Transactions Version 2 doesn't handle epoch overflow
correctly
Key: KAFKA-18661
URL: https://issues.apache.org/jira/browse/KAFKA-18661
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-18525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lianet Magrans resolved KAFKA-18525.
Resolution: Fixed
> Update the Test should run for async consumer
> --
Hi Almog,
I had similar thoughts as Lucas. When I read the KIP, I asked myself why
are the windows not specified on number of records instead of time if we
do not care about whether the event time of the records is in the time
range of the window?
In your motivation, you write that users mig
Hi Pramithas,
there was an attempt to introduce a code formatter in the following PR:
https://github.com/apache/kafka/pull/10428
However, the PR was never merged.
Best,
Bruno
On 23.01.25 17:29, pramithas dhakal wrote:
Hi Team,
As per the readme file I could see that there are two quality anal
Hi Almog,
this seems useful to me. I don't see anything wrong with the details
of the proposal.
More generally, I'd like to hear your thoughts on this vs. batching.
Given the motivation section, it sounds we actually want something
that I'd call "batching" rather than "windowing". If you do not r
Hello, quick update, there are 2 new blockers related to the new consumer
threading model:
- https://issues.apache.org/jira/browse/KAFKA-18645 -> PR already available
in review
- https://issues.apache.org/jira/browse/KAFKA-18641 -> Expecting a PR soon
Best,
Lianet
On Mon, Jan 27, 2025 at 6:55 PM
Gaurav, thanks for the KIP.
DA1: The four examples you give of improper usage of the existing
constructor are all Kafka usages, so arguably they are just bugs. Do we
know if ConfigException can be created/thrown by 3rd party code via our
pluggable interfaces? If there are any interface usages, can
[
https://issues.apache.org/jira/browse/KAFKA-17951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Schofield resolved KAFKA-17951.
--
Resolution: Fixed
> Rotate share partitions in share fetch
> -
[
https://issues.apache.org/jira/browse/KAFKA-18488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Schofield reopened KAFKA-18488:
--
Reopened while tracking down flakiness.
> Additional protocol tests for share consumption
19 matches
Mail list logo
