Chris Egerton created KAFKA-14059:
-
Summary: Replace EasyMock and PowerMock with Mockito in
WorkerSourceTaskTest
Key: KAFKA-14059
URL: https://issues.apache.org/jira/browse/KAFKA-14059
Project: Kafka
Chris Egerton created KAFKA-14060:
-
Summary: Replace EasyMock and PowerMock with Mockito in
AbstractWorkerSourceTaskTest
Key: KAFKA-14060
URL: https://issues.apache.org/jira/browse/KAFKA-14060
Chris Egerton created KAFKA-14058:
-
Summary: Replace EasyMock and PowerMock with Mockito in
ExactlyOnceWorkerSourceTaskTest
Key: KAFKA-14058
URL: https://issues.apache.org/jira/browse/KAFKA-14058
Hello everyone,
I'm ending this KIP vote as accepted with 4 binding +1s (John, Bruno,
David, Luke).
The wiki page has been updated and the corresponding code merged to trunk.
Thanks!
Guozhang
On Wed, Jul 6, 2022 at 7:02 PM Luke Chen wrote:
> Hi Guozhang,
>
> Removing the script-extention
Hi David,
Thanks for sharing this KIP! Really exciting to hear how we are changing
the protocol! The motivation section really made me realize how useful this
change will be.
I've done a first pass of the KIP, and may have more questions, but thought
I'd start with a few I thought of already.
Ron Dagostino created KAFKA-14057:
-
Summary: Support dynamic reconfiguration in KRaft remote
controllers
Key: KAFKA-14057
URL: https://issues.apache.org/jira/browse/KAFKA-14057
Project: Kafka
Ron Dagostino created KAFKA-14056:
-
Summary: Test reading of old messages formats in ZK-to-KRaft
upgrade test
Key: KAFKA-14056
URL: https://issues.apache.org/jira/browse/KAFKA-14056
Project: Kafka
Hi, Artem,
Thanks for the reply. It would be useful to add that clarification in the
description of the metric. Other than that, the KIP looks good to me.
Jun
On Tue, Jul 5, 2022 at 5:57 PM Artem Livshits
wrote:
> I've updated the KIP to clarify that the metric reflects the total amount
> of
Regarding the option to integrate repair logic in "latest", I understand your
concern about this approach: backward compatibility.
But we should have a consensus: the problem of data loss due to expand
partitions is indeed caused by kafka's own design mechanism. The user
configuration "latest"
Thank you, Jose.
Regards,
Rajini
On Fri, Jul 8, 2022 at 2:43 PM José Armando García Sancio
wrote:
> On Fri, Jul 8, 2022 at 6:37 AM Rajini Sivaram
> wrote:
> > We have a PR for batched offset fetch API, which is part of KIP-709 (
> >
>
On Fri, Jul 8, 2022 at 6:37 AM Rajini Sivaram wrote:
> We have a PR for batched offset fetch API, which is part of KIP-709 (
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173084258)
> that was opened a year ago, but didn't get merged because we didn't have
> time to merge
Hi Jose,
We have a PR for batched offset fetch API, which is part of KIP-709 (
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173084258)
that was opened a year ago, but didn't get merged because we didn't have
time to merge into 3.0: https://github.com/apache/kafka/pull/10964.
Submitted a PR with the fix: https://github.com/apache/kafka/pull/12392
In the PR I tried keeping the producer in a usable state after the forced
bump. I understand that it might be the cleanest solution, but the only
other option I know of is to transition into a fatal state, meaning that
the
[
https://issues.apache.org/jira/browse/KAFKA-13983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-13983.
---
Fix Version/s: 3.3.0
Reviewer: Manikumar
Resolution: Fixed
> Support special
Thanks, Artem. I am still +1.
On Fri, Jul 8, 2022 at 3:45 AM Artem Livshits
wrote:
>
> Hello,
>
> There was an additional discussion and the KIP got changed as a result of
> that. I would like to restart the vote on the updated
>
Dear Team,
We wanted to use kafka and therefore installed on ubuntu ( Ubuntu
20.04.4 LTS ) kafka ( 3.2.0 & zoopkeeper
3.6.3--6401e4ad2087061bc6b9f80dec2d69f2e3c8660a) .
With this installation, we wanted to connect to mysql server installed
on the same server.
Is it possible? If so what
16 matches
Mail list logo
