Re: Why need handle delete topic in topic change event

Hi 晓兵, I know what you mean now. Yes, that makes sense to me, as long as you confirmed that each topic deletion, we'll put a znode under "delete_topics". Please open a jira ticket and welcome to submit PR. Thank you. Luke On Tue, Oct 12, 2021 at 10:32 AM 方晓兵 <94fxiaob...@gmail.com> wrote: > Hi L

Re: Why need handle delete topic in topic change event

Hi Luke, What I mean is whether there is no need to listen to the topic znode deletion event, because `controllerContext#removeTopic` has been actively called after deleting znode in `TopicDeletionManager.completeDeleteTopic()`. Is it better for TopicChangeHandler to only handle child add events

Re: Why need handle delete topic in topic change event

Hi 晓兵, Are you saying we should not call `removeTopic` because the topic znode is deleted? Have a quick look at the `controllerContext#removeTopic` implementation, it looks like we only clean up the metrics, and local maps. Why is it a problem we called it here? Does it caused any error? Could you

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #516

See

Requesting Project Access

Hi, I am requesting access in order to make contributions to Kafka. My Jira and Wiki ID are both "masonlegere" Best, -- Mason Legere Software Engineer | Salesforce Mobile: 250-981-5209

[DISCUSS] KIP-781: Allow MirrorMaker 2 to override the client configurations

Hi Kafka dev, I hope to initiate the discussion of KIP-781: Allow MirrorMaker 2 to override the client configurations. https://cwiki.apache.org/confluence/display/KAFKA/KIP-781%3A+Allow+MirrorMaker+2+to+override+the+client+configurations I found this problem while testing the MirrorMaker 2 deplo

[jira] [Created] (KAFKA-13365) Allow MirrorMaker 2 to override the client configurations

Dongjin Lee created KAFKA-13365: --- Summary: Allow MirrorMaker 2 to override the client configurations Key: KAFKA-13365 URL: https://issues.apache.org/jira/browse/KAFKA-13365 Project: Kafka Issue

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #515

See Changes: -- [...truncated 493620 lines...] [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // stage [Pipeline] } [2021-1

[jira] [Created] (KAFKA-13364) SQL Processor Alerts Creation when Failed

Jyothiraditya Dandamudi created KAFKA-13364: --- Summary: SQL Processor Alerts Creation when Failed Key: KAFKA-13364 URL: https://issues.apache.org/jira/browse/KAFKA-13364 Project: Kafka

[jira] [Created] (KAFKA-13363) Add support for asynchronous authorization

Jeremy Whitlock created KAFKA-13363: --- Summary: Add support for asynchronous authorization Key: KAFKA-13363 URL: https://issues.apache.org/jira/browse/KAFKA-13363 Project: Kafka Issue Type:

[jira] [Resolved] (KAFKA-12802) Add a file based cache for consumed remote log metadata for each partition to avoid consuming again incase of broker restarts.

[ https://issues.apache.org/jira/browse/KAFKA-12802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-12802. - Resolution: Fixed merged the PR to trunk > Add a file based cache for consumed remote log metadata for

[jira] [Created] (KAFKA-13362) KafkaConnect authorization failure using SCRAM-SHA-512 and OPA

Olumide Ajiboye created KAFKA-13362: --- Summary: KafkaConnect authorization failure using SCRAM-SHA-512 and OPA Key: KAFKA-13362 URL: https://issues.apache.org/jira/browse/KAFKA-13362 Project: Kafka

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #514

See

Re: [DISCUSS] Apache Kafka 3.1.0 release

Hi Michael, Sure. I have updated the release plan to include it. Thanks for the heads up. Best, David On Mon, Oct 11, 2021 at 4:39 PM Mickael Maison wrote: > Hi David, > > You can add KIP-690 to the release plan. The vote passed months ago > and I merged the PR today. > > Thanks > > On Fri, Oc

Re: [DISCUSS] Apache Kafka 3.1.0 release

Hi David, You can add KIP-690 to the release plan. The vote passed months ago and I merged the PR today. Thanks On Fri, Oct 8, 2021 at 8:32 AM David Jacot wrote: > > Hi folks, > > Just a quick reminder that KIP Freeze is next Friday, October 15th. > > Cheers, > David > > On Wed, Sep 29, 2021 at

[jira] [Resolved] (KAFKA-10777) Add additional configuration to control MirrorMaker 2 internal topics naming convention

[ https://issues.apache.org/jira/browse/KAFKA-10777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-10777. Resolution: Fixed > Add additional configuration to control MirrorMaker 2 internal topics

Re: [DISCUSS] KIP-779: Allow Source Tasks to Handle Producer Exceptions

Good morning, Bumping this for visibility. I would like this to go into the next release. KIP freeze is Friday. Any comments and feedback are welcome. Knowles On Tue, Oct 5, 2021 at 4:24 PM Knowles Atchison Jr wrote: > Hello all, > > I would like to discuss the following KIP: > > > https://cw

Why need handle delete topic in topic change event

Hi Team, I have a problem when I study kafka code in version 2.8.0. I see `controllerContext.removeTopic(topic)` have been called in `TopicDeletionManager.completeDeleteTopic()`. TopicChangeHandler not only listen to child delete but also listen to child add. So every time a topic is deleted,

Why need handle delete topic in topic change event

Hi Team, I have a problem when I study kafka code in version 2.8.0. I see `controllerContext.removeTopic(topic)` have been called in `TopicDeletionManager.completeDeleteTopic()`. TopicChangeHandler not only listen to child delete but also listen to child add. So every time a topic is deleted,

Re: [DISCUSS] Apache Kafka 2.6.3 release

Hi Israel, The DISCUSS threads for releases are typically used to show support or raise concerns about a release. They are also used if you want to request a fix to be backported. The next step is for me to build the first RC. I'll open a VOTE thread once I have built it. Thanks On Sat, Oct 9,