Re: Request to be added as a contributor

Hello, I've added you as a contributor to Kafka. Cheers, Guozhang On Wed, Jul 31, 2019 at 5:31 PM Tharindu Amila < tharindu.am...@instaclustr.com> wrote: > Hi Team, > > Request you to add me to the contributor list. Jira username : tharindu > > Thanks and Regards, > > > *Tharindu

Jenkins build is back to normal : kafka-2.3-jdk8 #79

See

Build failed in Jenkins: kafka-trunk-jdk11 #724

See Changes: [github] MINOR: Small cleanups in TopicCommand describe handling (#7136) [junrao] Update KafkaConfig.scala (#7113) [wangguoz] KAFKA-8179: PartitionAssignorAdapter (#7110) [cmccabe] MINOR: Add

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

See Changes: [github] MINOR: Tolerate limited data loss for upgrade tests with old message [github] MINOR: Small cleanups in TopicCommand describe handling (#7136) [junrao] Update KafkaConfig.scala (#7113)

Request to be added as a contributor

Hi Team, Request you to add me to the contributor list. Jira username : tharindu Thanks and Regards, *Tharindu Amila**Software Engineer* Read our latest technical blog

Dynamic configuration of interbroker SSL certificates

Hi all, I'm having an issue with dynamic configuration of interbroker SSL certificates (in Kafka 2.3.0) that I'm hoping someone can give me insight on. I've previously posted something similar on the Users email list, but I think it will need some help from developers experienced with how the

Re: [VOTE] KIP-221: Enhance KStream with Connecting Topic Creation and Repartition Hint

+1 (binding) On 7/31/19 8:36 AM, Guozhang Wang wrote: > Thanks for the update! +1 (binding). > > On Tue, Jul 30, 2019 at 11:42 PM Levani Kokhreidze > wrote: > >> Hello Guozhang, >> >> Thanks for the feedback. That’s an interesting point. To be honest, I >> totally missed it. I wasn’t aware

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

See

[jira] [Resolved] (KAFKA-8704) Add PartitionAssignor adapter for backwards compatibility

[ https://issues.apache.org/jira/browse/KAFKA-8704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-8704. -- Resolution: Fixed Fix Version/s: 2.4.0 > Add PartitionAssignor adapter for backwards

Re: [DISCUSS] KIP-487: Automatic Topic Creation on Producer

Hi Mickael, I think you bring up a good point. It would be better if we didn't ever have to set up client-side configuration for this feature, and KIP-464 would let us skip this entirely. On Wed, Jul 31, 2019, at 09:19, Justine Olshan wrote: > Hi Mickael, > I agree that KIP-464 works on newer

Re: [VOTE] KIP-455: Create an Administrative API for Replica Reassignment

Hi Jun, Thanks for taking another look at this. On Wed, Jul 31, 2019, at 09:22, Jun Rao wrote: > Hi, Stan, > > Thanks for the explanation. > > 10. If those new fields in LeaderAndIsr are only needed for future work, > perhaps they should be added when we do the future work instead of now? I

Re: [VOTE] KIP-455: Create an Administrative API for Replica Reassignment

Hi, Stan, Thanks for the explanation. 10. If those new fields in LeaderAndIsr are only needed for future work, perhaps they should be added when we do the future work instead of now? Jun On Wed, Jul 31, 2019 at 2:30 AM Stanislav Kozlovski wrote: > Hey Jun, > > I think I can answer some of

Re: [DISCUSS] KIP-487: Automatic Topic Creation on Producer

Hi Mickael, I agree that KIP-464 works on newer brokers, but I was a bit worried how things would play out on older brokers that* do not *have KIP 464 included. Is it enough to throw an error in this case when producer configs are not specified? Thanks, Justine On Wed, Jul 31, 2019 at 9:10 AM

Re: [DISCUSS] KIP-487: Automatic Topic Creation on Producer

Hi Justine, We can rely on KIP-464 which allows to omit the partition count or replication factor when creating a topic. In that case, the broker defaults are used. On Wed, Jul 31, 2019 at 4:55 PM Justine Olshan wrote: > > Michael, > That makes sense to me! > To clarify, in the current state of

Re: [DISCUSS] KIP-487: Automatic Topic Creation on Producer

Michael, That makes sense to me! To clarify, in the current state of the KIP, the producer does not rely on the broker to autocreate--if the broker's config is disabled, then the producer can autocreate on its own with a create topic request (the same type of request the admin client uses).

Re: [VOTE] KIP-221: Enhance KStream with Connecting Topic Creation and Repartition Hint

Thanks for the update! +1 (binding). On Tue, Jul 30, 2019 at 11:42 PM Levani Kokhreidze wrote: > Hello Guozhang, > > Thanks for the feedback. That’s an interesting point. To be honest, I > totally missed it. I wasn’t aware that there’s `groupBy` possibility on > KTable. > I don’t see any

[jira] [Resolved] (KAFKA-8688) Upgrade system tests fail due to data loss with older message format

[ https://issues.apache.org/jira/browse/KAFKA-8688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-8688. --- Resolution: Fixed Reviewer: Ismael Juma Fix Version/s: 2.4.0 > Upgrade

Build failed in Jenkins: kafka-0.10.2-jdk7 #243

See Changes: [jason] KAFKA-8722; Ensure record CRC is always verified when appending to log -- [...truncated 1.12 MB...]

Re: [DISCUSS] KIP-499 - Unify connection name flag for command line tool

Hi Jason, Thanks for looking at this! I wasn't exactly sure what to put in the compatibility section. I wrote the KIP thinking that we should probably mark the old arguments for deprecation for a release or two before actually removing them. I'm happy to change this either way if it's

Re: [DISCUSS] KIP-487: Automatic Topic Creation on Producer

Hi Justine, Thanks for the response! In my opinion, it would be better if the producer did not rely at all on the broker auto create feature as this is what we're aiming to deprecate. When requesting metadata we can set the "allow_auto_topic_creation" field to false to avoid the broker auto

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

See Changes: [github] MINOR: Refactor abstractConfig#configuredInstance (#7129) -- [...truncated 2.57 MB...]

Re: [ANNOUNCE] Apache Kafka 2.3.0

Hi, It looks like the protocol page was not updated. It still only lists 2.2 APIs. http://kafka.apache.org/protocol Thanks On Tue, Jul 2, 2019 at 2:05 AM Colin McCabe wrote: > > Hi Mickael, > > Thanks for pointing this out. It should be fixed now. > > best, > Colin > > On Mon, Jul 1, 2019, at

Re: [DISCUSS] KIP-498: Add client-side configuration for maximum response size to protect against OOM

Hi Alex. A rejected alternative is to try to do SSL handshake from the plaintext transport layer. This couples various transport layers and is inflexible to adding new transport layers in the future. Further, if the plaintext transport layer does SSL handshake, it will always get an error,

Re: [VOTE] KIP-455: Create an Administrative API for Replica Reassignment

Hey Jun, I think I can answer some of your questions on behalf of Colin -- he can confirm if I'm correct > 10. The KIP adds two new fields (AddingReplicas and RemovingReplicas) to LeaderAndIsr request. Could you explain how these 2 fields will be used? Sorry for not explaining this in the KIP -

[jira] [Resolved] (KAFKA-8722) Data crc check repair

[ https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-8722. Resolution: Fixed Fix Version/s: (was: 0.10.2.2) 0.10.2.3 >

[VOTE] KIP-373: Allow users to create delegation tokens for other users

Hi All, I'd like to start a vote on this KIP. https://cwiki.apache.org/confluence/display/KAFKA/KIP-373%3A+Allow+users+to+create+delegation+tokens+for+other+users To summarize it: the proposed feature would allow users (usually superusers) to create delegation tokens for other users. This is

Re: [DISCUSS] KIP-373: Allow users to create delegation tokens for other users

Hi Folks, I'm starting a vote on this. Viktor On Thu, Jun 27, 2019 at 12:02 PM Viktor Somogyi-Vass < viktorsomo...@gmail.com> wrote: > Hi Folks, > > I took over this issue from Manikumar. Recently another motivation have > been raised in Spark for this (SPARK-28173) and I think it'd be great

[jira] [Created] (KAFKA-8739) rejoining broker fails to sanity check existing log segments

sanjiv marathe created KAFKA-8739: - Summary: rejoining broker fails to sanity check existing log segments Key: KAFKA-8739 URL: https://issues.apache.org/jira/browse/KAFKA-8739 Project: Kafka

Re: Request to be a contributor

Done. On 7/30/19 4:30 PM, Michael Carter wrote: > Hi dev, > > Can I please be added to the contributor list? > My JIRA username is michael_carter > > Cheers, > Michael > signature.asc Description: OpenPGP digital signature

Re: [VOTE] KIP-221: Enhance KStream with Connecting Topic Creation and Repartition Hint

Hello Guozhang, Thanks for the feedback. That’s an interesting point. To be honest, I totally missed it. I wasn’t aware that there’s `groupBy` possibility on KTable. I don’t see any reasons why not to add same functionality to KTable interface. I’ve updated the KIP: