Re: access for KIP

Done. Cheers. Guozhang On Wed, Jun 20, 2018 at 5:18 PM, Lei Chen wrote: > Hi, there, > > I'd like to request permission to the kafka space in our ASF cwiki, to be > able > to create KIPs. > > Username: leyncl > email: ley...@gmail.com > > Thanks! > -- -- Guozhang

Re: cwiki access for KIP

sweet, thanks! On Wed, Jun 20, 2018 at 11:02 PM, Matthias J. Sax wrote: > Done. > > On 6/20/18 11:15 AM, Matthias Wessendorf wrote: > > Hi, > > > > I'd like to request permission to the kafka space in our ASF cwiki, to be > > able to create KIPs. > > > > Username: matzew > > email:

Re: access for KIP

You are added already. On 6/20/18 5:18 PM, Lei Chen wrote: > Hi, there, > > I'd like to request permission to the kafka space in our ASF cwiki, to be able > to create KIPs. > > Username: leyncl > email: ley...@gmail.com > > Thanks! > signature.asc Description: OpenPGP digital signature

Re: [DISCUSS] KIP-221: Repartition Topic Hints in Streams

No worries. It's just good to know. It seems that some other people are interested to drive this further. So we will just "reassign" it to them. Thanks for letting us know. -Matthias On 6/20/18 2:51 PM, Jeyhun Karimov wrote: > Hi Matthias, all, > > Currently, I am not able to complete this

[Discuss] KIP-321: Add method to get TopicNameExtractor in TopologyDescription

Hello Everyone, I have created a new KIP to discuss extending TopologyDescription. You can find it here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-321%3A+Add+method+to+get+TopicNameExtractor+in+TopologyDescription Please provide any feedback that you might have. Best, Nishanth

Re: [DISCUSS] KIP-318: Make Kafka Connect Source idempotent

Hi Randall Thanks for your feedback 1) user can override: yes they can but they most surely won't know about it. I didn't know about this improvement until I got on twitter and exchanged with Ismael. I would say most users don't even know Kafka connect is running with acks=all. My understanding

[jira] [Resolved] (KAFKA-7072) Kafka Streams may drop rocksb window segments before they expire

[ https://issues.apache.org/jira/browse/KAFKA-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-7072. -- Resolution: Fixed > Kafka Streams may drop rocksb window segments before they expire >

access for KIP

Hi, there, I'd like to request permission to the kafka space in our ASF cwiki, to be able to create KIPs. Username: leyncl email: ley...@gmail.com Thanks!

Re: [DISCUSS] KIP-315: Stream Join Sticky Assignor

Hi Mike, Thanks for sharing your feedbacks and the blocker features for Kafka Streams. They are very helpful. Guozhang On Wed, Jun 20, 2018 at 2:47 PM, Mike Freyberger wrote: > Matthias, > > Thanks for the feedback. For our use case, we have some complexities that > make using the existing

Re: [VOTE] KIP-291: Have separate queues for control requests and data requests

+1 -Harsha On Wed, Jun 20, 2018, at 5:15 AM, Thomas Crayford wrote: > +1 (non-binding) > > On Tue, Jun 19, 2018 at 8:20 PM, Lucas Wang wrote: > > > Hi Jun, Ismael, > > > > Can you please take a look when you get a chance? Thanks! > > > > Lucas > > > > On Mon, Jun 18, 2018 at 1:47 PM, Ted Yu

Re: [DISCUSS] - KIP-314: KTable to GlobalKTable Bi-directional Join

Hello Adam, Thanks for proposing the KIP. A few meta comments: 1. As Matthias mentioned, the current GlobalKTable is designed to be read-only, and not driving any computations (btw the global store backing a GlobalKTable should also be read-only). Behind the scene the global store updating task

Re: [DISCUSS] KIP-319: Replace segments with segmentSize in WindowBytesStoreSupplier

Hello John, Thanks for the KIP. Should we consider making the change on `Stores#persistentWindowStore` parameters as well? Guozhang On Wed, Jun 20, 2018 at 1:31 PM, John Roesler wrote: > Hi Ted, > > Ah, when you made that comment to me before, I thought you meant as opposed > to

Re: [DISCUSS] KIP-221: Repartition Topic Hints in Streams

Hi Matthias, all, Currently, I am not able to complete this KIP. Please accept my apologies for that. Cheers, Jeyhun On Mon, Jun 11, 2018 at 2:25 AM Matthias J. Sax wrote: > What is the status of this KIP? > > -Matthias > > > On 2/13/18 1:43 PM, Matthias J. Sax wrote: > > Is there any update

Re: [DISCUSS] KIP-315: Stream Join Sticky Assignor

Matthias, Thanks for the feedback. For our use case, we have some complexities that make using the existing Streams API more complicated than using the Kafka Consumer directly. - We are doing async processing, which I don't think is currently available (KIP-311 is handling this). - Our

Re: [DISCUSS] KIP-315: Stream Join Sticky Assignor

Mike, thanks a lot for the KIP. I am wondering, why Streams API cannot be used for perform the join? Would be good to understand the advantage of adding a `StickyStreamJoinAssignor` compared to using Streams API? Atm, it seems to be a redundant feature to me. -Matthias On 6/20/18 1:07 PM, Mike

Re: cwiki access for KIP

Done. On 6/20/18 11:15 AM, Matthias Wessendorf wrote: > Hi, > > I'd like to request permission to the kafka space in our ASF cwiki, to be > able to create KIPs. > > Username: matzew > email: mat...@apache.org > > Thanks! > Matthias > signature.asc Description: OpenPGP digital signature

[jira] [Created] (KAFKA-7082) Concurrent createTopics calls may throw NodeExistsException

Ismael Juma created KAFKA-7082: -- Summary: Concurrent createTopics calls may throw NodeExistsException Key: KAFKA-7082 URL: https://issues.apache.org/jira/browse/KAFKA-7082 Project: Kafka Issue

Re: [DISCUSS] KIP-319: Replace segments with segmentSize in WindowBytesStoreSupplier

Hi Ted, Ah, when you made that comment to me before, I thought you meant as opposed to "segments". Now it makes sense that you meant as opposed to "segmentSize". I named it that way to match the peer method "windowSize", which is also a quantity of milliseconds. I agree that "interval" is more

[VOTE] 2.0.0 RC0

Hello Kafka users, developers and client-developers, This is the first candidate for release of Apache Kafka 2.0.0. This is a major version release of Apache Kafka. It includes 40 new KIPs and several critical bug fixes. Please see the 2.0.0 release plan for more details:

[DISCUSS] KIP-315: Stream Join Sticky Assignor

Hi everybody, I’ve created a proposal document for KIP-315 which outlines the motivation of adding a new partition assignment strategy that can used for streaming join use cases. It’d be great to get feedback on the overall idea and the proposed implementation. KIP Link:

Jenkins build is back to normal : kafka-2.0-jdk8 #48

See

cwiki access for KIP

Hi, I'd like to request permission to the kafka space in our ASF cwiki, to be able to create KIPs. Username: matzew email: mat...@apache.org Thanks! Matthias -- Matthias Wessendorf github: https://github.com/matzew twitter: http://twitter.com/mwessendorf

Re: [DISCUSS] KIP-319: Replace segments with segmentSize in WindowBytesStoreSupplier

Normally size is not measured in time unit, such as milliseconds.  How about naming the new method segmentInterval ? Thanks Original message From: John Roesler Date: 6/20/18 10:45 AM (GMT-08:00) To: dev@kafka.apache.org Subject: [DISCUSS] KIP-319: Replace segments with

[jira] [Created] (KAFKA-7081) Add describe all topics API to AdminClient

Manikumar created KAFKA-7081: Summary: Add describe all topics API to AdminClient Key: KAFKA-7081 URL: https://issues.apache.org/jira/browse/KAFKA-7081 Project: Kafka Issue Type: Improvement

[DISCUSS] KIP-319: Replace segments with segmentSize in WindowBytesStoreSupplier

Hello All, I'd like to propose KIP-319 to fix an issue I identified in KAFKA-7080. Specifically, we're creating CachingWindowStore with the *number of segments* instead of the *segment size*. Here's the jira: https://issues.apache.org/jira/browse/KAFKA-7080 Here's the KIP:

Re: [DISCUSS] KIP-318: Replace segments with segmentSize in WindowBytesStoreSupplier

Oops! It looks like 318 was taken. I'll re-send this message to a new thread. On Wed, Jun 20, 2018 at 12:40 PM John Roesler wrote: > Hello All, > > I'd like to propose KIP-318 to fix an issue I identified in KAFKA-7080. > Specifically, we're creating CachingWindowStore with the *number of >

[DISCUSS] KIP-318: Replace segments with segmentSize in WindowBytesStoreSupplier

Hello All, I'd like to propose KIP-318 to fix an issue I identified in KAFKA-7080. Specifically, we're creating CachingWindowStore with the *number of segments* instead of the *segment size*. Here's the jira: https://issues.apache.org/jira/browse/KAFKA-7080 Here's the KIP:

[jira] [Resolved] (KAFKA-6546) Add ENDPOINT_NOT_FOUND_ON_LEADER error code for missing listener

[ https://issues.apache.org/jira/browse/KAFKA-6546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-6546. --- Resolution: Fixed Reviewer: Ismael Juma Fix Version/s: (was: 2.1.0)

[jira] [Created] (KAFKA-7080) WindowStoreBuilder incorrectly initializes CachingWindowStore

John Roesler created KAFKA-7080: --- Summary: WindowStoreBuilder incorrectly initializes CachingWindowStore Key: KAFKA-7080 URL: https://issues.apache.org/jira/browse/KAFKA-7080 Project: Kafka

Re: [DISCUSS] KIP-316: Command-line overrides for ConnectDistributed worker properties

My only concern with this proposal is that it adds yet another way to specify configuration properties, making it a bit more difficult to track down how/whether a configuration property has been set. Configuring Kafka Connect is already too challenging, so we need to be very clear that this

Re: [VOTE] KIP-316: Command-line overrides for ConnectDistributed worker properties

IMO we should not request a vote without additional time for discussion. Best regards, Randall On Wed, Jun 20, 2018 at 7:29 AM, Jakub Scholz wrote: > +1 (non-binding) > > On Mon, Jun 18, 2018 at 8:42 PM Kevin Lafferty > wrote: > > > Hi all, > > > > I got a couple notes of interest on the

Re: [DISCUSS] KIP-318: Make Kafka Connect Source idempotent

Thanks for starting this conversation, Stephane. I have a few questions. The worker already accepts nearly all producer properties already, and all `producer.*` properties override any hard-coded properties defined in `Worker.java`. So isn't it currently possible for a user to define these

Build failed in Jenkins: kafka-2.0-jdk8 #47

See Changes: [ismael] MINOR: Use exceptions in o.a.k.common if possible and deprecate ZkUtils -- [...truncated 433.76 KB...] kafka.zookeeper.ZooKeeperClientTest >

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

See

Re: [DISCUSS] KIP-291: Have separate queues for control requests and data requests

Hi Lucas, Sorry for the delay, just had a look at this. A couple of questions: - did you notice any positive change after implementing this KIP? I'm wondering if you have any experimental results that show the benefit of the two queues. - priority is usually not sufficient in addressing the

Re: [VOTE] KIP-316: Command-line overrides for ConnectDistributed worker properties

+1 (non-binding) On Mon, Jun 18, 2018 at 8:42 PM Kevin Lafferty wrote: > Hi all, > > I got a couple notes of interest on the discussion thread and no > objections, so I'd like to kick off a vote. This is a very small change. > > KIP: > >

[jira] [Created] (KAFKA-7079) ValueTransformer#transform does not pass the key

Hashan Gayasri Udugahapattuwa created KAFKA-7079: Summary: ValueTransformer#transform does not pass the key Key: KAFKA-7079 URL: https://issues.apache.org/jira/browse/KAFKA-7079

Re: [VOTE] KIP-291: Have separate queues for control requests and data requests

+1 (non-binding) On Tue, Jun 19, 2018 at 8:20 PM, Lucas Wang wrote: > Hi Jun, Ismael, > > Can you please take a look when you get a chance? Thanks! > > Lucas > > On Mon, Jun 18, 2018 at 1:47 PM, Ted Yu wrote: > > > +1 > > > > On Mon, Jun 18, 2018 at 1:04 PM, Lucas Wang > wrote: > > > > > Hi

[jira] [Resolved] (KAFKA-3018) Kafka producer hangs on producer.close() call if the producer topic contains single quotes in the topic name

[ https://issues.apache.org/jira/browse/KAFKA-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3018. -- Resolution: Duplicate Resolving this as duplicate of KAFKA-5098.  Please reopen if you think otherwise

[jira] [Created] (KAFKA-7078) Kafka 1.0.1 Broker version crashes when deleting log

xiaojing zhou created KAFKA-7078: Summary: Kafka 1.0.1 Broker version crashes when deleting log Key: KAFKA-7078 URL: https://issues.apache.org/jira/browse/KAFKA-7078 Project: Kafka Issue

[DISCUSS] KIP-318: Make Kafka Connect Source idempotent

KIP link: https://cwiki.apache.org/confluence/display/KAFKA/KIP-318%3A+Make+Kafka+Connect+Source+idempotent By looking at the code, it seems Worker.java is where the magic happens, but do we need to also operate changes to KafkaBasedLog.java (~line 241) ? Love to hear your thoughts!

[jira] [Created] (KAFKA-7077) producerProps.put(ProducerConfig.MAX_IN_FLIGHT_REQUESTS_PER_CONNECTION, "5") producerProps.put(ProducerConfig.ENABLE_IDEMPOTENCE, true)

Stephane Maarek created KAFKA-7077: -- Summary: producerProps.put(ProducerConfig.MAX_IN_FLIGHT_REQUESTS_PER_CONNECTION, "5") producerProps.put(ProducerConfig.ENABLE_IDEMPOTENCE, true) Key: KAFKA-7077 URL: