Re: [DISCUSS] KIP-307: Allow to define custom processor names with KStreams DSL

Hello Florian, Really appreciate you for your patience. I know that we've discussed about the approach to adding overloaded functions and rejected it early on. But looking deeper into the current PR I realized that this approach has a danger of great API confusions to users (I tried to explain my

Re: Request permission to open a Kafka KIP

Hello Yaodong, I've added you to the wiki space. But I cannot find your account in JIRA ( https://issues.apache.org/jira/projects/KAFKA/summary), have you created the account? Guozhang On Fri, Dec 14, 2018 at 2:24 PM Yaodong Yang wrote: > Dear folks, > > I'm Yaodong Yang, I'm requesting the

Jenkins build is back to normal : kafka-trunk-jdk8 #3263

See

Re: [DISCUSS] KIP-404: Add Kafka Connect configuration parameter for disabling WADL output on OPTIONS request

Konstantine and Jason, I do agree that this functionality was not documented, and most likely not intended to be present. Therefore we can consider it as not a part of the public interface, and current behavior as not expected. Hence, addressing the issue by just disabling the WADL output seems li

Re: [DISCUSS] KIP-401 TransformerSupplier/ProcessorSupplier enhancements

Matthias, Thanks for your feedbacks. Regarding the last option to catch "store exist already" exception and fallback to connect stores, I'm a bit concerned it may be hiding actual user bugs. Thinking about Paul's proposal and your suggestion again, I'd like to propose another alternative somewhe

Re: [DISCUSS] KIP-404: Add Kafka Connect configuration parameter for disabling WADL output on OPTIONS request

Hi Alex, thanks for working on this and identifying the need to address this issue. I see under Rejected Alternatives that the option to disable this feature has been considered already. However, I'd like to return a bit to this option and highlight the following: * Exposing this request was not

Re: [DISCUSS] KIP-404: Add Kafka Connect configuration parameter for disabling WADL output on OPTIONS request

Hi Alex, I think WADL support was likely unintentional, so this could be treated as more of a bug. Unless we think it's a good idea to support it going forward, I'd suggest going with the rejected alternative of just turning it off. What do you think? Thanks, Jason On Fri, Dec 14, 2018 at 3:06 P

[VOTE] KIP-404: Add Kafka Connect configuration parameter for disabling WADL output on OPTIONS request

Hi all, I would like to call for votes on KIP-404 , it proposes to let users disable WADL output for Connect REST endpoints. There was no objection r

Re: [DISCUSS] KIP-404: Add Kafka Connect configuration parameter for disabling WADL output on OPTIONS request

Thanks, everyone for taking the time to review the KIP. It looks like there are no major objections on it, so I will start voting thread. Regards, Alex. On Thu, Dec 13, 2018 at 3:50 PM Randall Hauch wrote: > Thanks, Alex. The KIP looks good to me. > > Randall > > On Wed, Dec 12, 2018 at 10:0

[jira] [Created] (KAFKA-7740) Kafka Admin Client should be able to dynamically change the traffic quota configurations for users and clients

Yaodong Yang created KAFKA-7740: --- Summary: Kafka Admin Client should be able to dynamically change the traffic quota configurations for users and clients Key: KAFKA-7740 URL: https://issues.apache.org/jira/browse/KA

Request permission to open a Kafka KIP

Dear folks, I'm Yaodong Yang, I'm requesting the permission to open a KIP for a new improvement I want to contribute. My cwiki id: yaodong66, my name: Yaodong Yang. Please feel free to let me know if you need anything from my side. Thanks! Yaodong

[jira] [Resolved] (KAFKA-2334) Prevent HW from going back during leader failover

[ https://issues.apache.org/jira/browse/KAFKA-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-2334. Resolution: Fixed Fix Version/s: 2.2.0 > Prevent HW from going back during leader fa

Build failed in Jenkins: kafka-2.1-jdk8 #85

See Changes: [wangguoz] MINOR: Replace tbd with the actual link for out-of-ordering data (#6035) -- [...truncated 909.92 KB...] kafka.security.auth.SimpleAclAuthorizerTest >

Re: what happens when a vote ends with no votes?

I guess it would be different if you had one vote instead of none. The norm seems to be to just continue nagging people in the [VOTE] thread until you accrue the needed votes. If I understand the policy, it's just there to prevent three committers from railroading a KIP though without giving every

[jira] [Resolved] (KAFKA-7374) Tiered Storage

[ https://issues.apache.org/jira/browse/KAFKA-7374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani resolved KAFKA-7374. --- Resolution: Duplicate > Tiered Storage > -- > > K

Re: [DISCUSS] KIP-382: MirrorMaker 2.0

Thanks Sönke, you're spot-on. I don't want MM2 to wait for Connect features that don't exist yet, especially if MM2 is the primary use case for them. Moreover, I think MM2 can drive and inform some of these features, which only makes sense if we adopt MM2 first. Ryanne On Fri, Dec 14, 2018, 9:03

RE: [VOTE] [REMINDER] KIP-383 Pluggable interface for SSL Factory

So far, there are no votes on this KIP. Please help me fix KAFKA-6654 by voting for this fix. Improvement comments are also welcome. -Original Message- From: Pellerin, Clement Sent: Tuesday, December 11, 2018 2:17 PM To: dev@kafka.apache.org Subject: RE: [VOTE] KIP-383 Pluggable interfac

RE: what happens when a vote ends with no votes?

I think that should be made clearer in the wiki because right now it says: The vote should remain open for 72 hours. I'm sure I'm not alone to think this means the vote closes after 72h. I can keep the vote open and send a reminder, but technically, that's the same as a new vote when there were

Re: what happens when a vote ends with no votes?

A vote must stay open for _at least_ 72 hours to ensure people have a chance to see it. Apart from that these's no upper bound for the duration, some vote threads are open for weeks On Fri, Dec 14, 2018 at 8:29 PM Harsha wrote: > > Hi, >It might have slipped through. You can try calling ou

Re: what happens when a vote ends with no votes?

Hi, It might have slipped through. You can try calling out VOTE again on the KIP. Thanks, Harsha On Fri, Dec 14, 2018, at 12:19 PM, Pellerin, Clement wrote: > I called a vote on KIP-383 more than 72h ago but it attracted no votes > and no comments. > The rule requires lazy majority which

what happens when a vote ends with no votes?

I called a vote on KIP-383 more than 72h ago but it attracted no votes and no comments. The rule requires lazy majority which demands at least 3 binding votes. What happens next? -Original Message- From: Pellerin, Clement Sent: Tuesday, December 11, 2018 2:17 PM To: dev@kafka.apache.org

[jira] [Created] (KAFKA-7739) Kafka Tiered Storage

Sriharsha Chintalapani created KAFKA-7739: - Summary: Kafka Tiered Storage Key: KAFKA-7739 URL: https://issues.apache.org/jira/browse/KAFKA-7739 Project: Kafka Issue Type: New Feature

Build failed in Jenkins: kafka-trunk-jdk8 #3262

See Changes: [github] MINOR: Replace tbd with the actual link for out-of-ordering data (#6035) -- [...truncated 2.24 MB...] > Task :streams:upgrade-system-tests-0101:clas

Re: [DISCUSS] KIP-307: Allow to define custom processor names with KStreams DSL

Hi Florian, Sorry about the run-around of rejecting the original proposal, only to return to it later on. Hopefully, it's more encouraging than frustrating that we're coming around to your initial way of thinking. Thanks! -John On Thu, Dec 13, 2018 at 4:28 PM Florian Hussonnois wrote: > Hi all

[jira] [Created] (KAFKA-7738) Track partition leader epochs in client metadata

David Arthur created KAFKA-7738: --- Summary: Track partition leader epochs in client metadata Key: KAFKA-7738 URL: https://issues.apache.org/jira/browse/KAFKA-7738 Project: Kafka Issue Type: Impr

Re: Request permission to create KIP

Done. On 12/14/18 7:05 AM, hu wenze wrote: > Hi! Thanks for reading the email; > I want to create a new KIP, but I don't have permisiion; > > My wiki Id: laomei > > Thanks! > signature.asc Description: OpenPGP digital signature

Request permission to create KIP

Hi! Thanks for reading the email; I want to create a new KIP, but I don't have permisiion; My wiki Id: laomei Thanks!

[jira] [Created] (KAFKA-7737) Consolidate InitProducerId API

Viktor Somogyi created KAFKA-7737: - Summary: Consolidate InitProducerId API Key: KAFKA-7737 URL: https://issues.apache.org/jira/browse/KAFKA-7737 Project: Kafka Issue Type: Task Com

[jira] [Created] (KAFKA-7736) Consolidate Map usages in TransactionManager

Viktor Somogyi created KAFKA-7736: - Summary: Consolidate Map usages in TransactionManager Key: KAFKA-7736 URL: https://issues.apache.org/jira/browse/KAFKA-7736 Project: Kafka Issue Type: Task

Re: [DISCUSS] KIP-382: MirrorMaker 2.0

Hi Jun, I believe Ryanne's idea is to run multiple workers per MM cluster-node, one per target cluster. So in essence you'd specify three clusters in the MM config and MM would then instantiate one worker per cluster. Every MM connector would then be deployed to the appropriate (internal) worker t

Re: [DISCUSS] KIP-402: Improve fairness in SocketServer processors

Hi Harsha, I am not sure if we have numbers for connection bursts. But since we have the code, I can run some tests with and without the change and provided the results. Hi Edo, There is no reason why we can't make num.network.threads a listener config that allows different listeners to use diff

Re: [DISCUSS] KIP-402: Improve fairness in SocketServer processors

Hi Rajini thanks for the KIP! I noticed (from the KIP text) the new > Config option: Name: max.connections > The config may be prefixed with listener prefix to specify different limits for different listeners, enabling inter-broker connections to be created even if there are a large number of c

[jira] [Created] (KAFKA-7735) StateChangeLogMerger tool can not work due to incorrect topic regular matches

Fangbin Sun created KAFKA-7735: -- Summary: StateChangeLogMerger tool can not work due to incorrect topic regular matches Key: KAFKA-7735 URL: https://issues.apache.org/jira/browse/KAFKA-7735 Project: Kafk

Jenkins build is back to normal : kafka-trunk-jdk8 #3260

See

Jenkins build is back to normal : kafka-trunk-jdk11 #158

See