Re: [ANNOUNCE] New committer: Onur Karaman

Congratulations Onur!! On Tue, 7 Nov 2017 at 06:30, Jaikiran Pai wrote: > Congratulations Onur! > > -Jaikiran > > > On 06/11/17 10:54 PM, Jun Rao wrote: > > Hi, everyone, > > > > The PMC of Apache Kafka is pleased to announce a new Kafka committer Onur > > Karaman. > >

Re: [ANNOUNCE] New committer: Onur Karaman

Congratulations Onur! -Jaikiran On 06/11/17 10:54 PM, Jun Rao wrote: Hi, everyone, The PMC of Apache Kafka is pleased to announce a new Kafka committer Onur Karaman. Onur's most significant work is the improvement of Kafka controller, which is the brain of a Kafka cluster. Over time, we

Re: [ANNOUNCE] New committer: Onur Karaman

Thanks everyone! On Mon, Nov 6, 2017 at 3:31 PM, Becket Qin wrote: > Congrats, Onur! > > On Mon, Nov 6, 2017 at 2:45 PM, James Cheng wrote: > > > Congrats Onur! Well deserved! > > > > -James > > > > > On Nov 6, 2017, at 9:24 AM, Jun Rao

Re: [VOTE] KIP-159: Introducing Rich functions to Streams

I Aggree completely. Exposing this information in a place where it has no _natural_ belonging might really be a bad blocker in the long run. Concerning your first point. I would argue its not to hard to have a user keep track of these. If we still don't want the user to keep track of these I

Re: [DISCUSS] KIP-219 - Improve Quota Communication

Hi Jun, Hmm, even if a connection is closed by the client when the channel is muted. After the channel is unmuted, it seems Selector.select() will detect this and close the socket. It is true that before the channel is unmuted the socket will be in a CLOSE_WAIT state though. So having an

Re: [DISCUSS] KIP-219 - Improve Quota Communication

Hi Rajini, Thanks for the detail explanation. Please see the reply below: 2. Limiting the throttle time to connection.max.idle.ms on the broker side is probably fine. However, clients may have a different configuration of connection.max.idle.ms and still reconnect before the throttle time (which

Re: [VOTE] KIP-159: Introducing Rich functions to Streams

Regarding the API design (the proposed set of overloads v.s. one overload on #map to enrich the record), I think what we have represents a good trade-off between API succinctness and user convenience: on one hand we definitely want to keep as fewer overloaded functions as possible. But on the

Jenkins build is back to normal : kafka-trunk-jdk7 #2951

See

[GitHub] kafka pull request #4186: [WIP] KAFKA-6179: Clear min timestamp tracker upon...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/4186 [WIP] KAFKA-6179: Clear min timestamp tracker upon partition queue cleanup You can merge this pull request into a Git repository by running: $ git pull

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

See Changes: [okaraman] KAFKA-5894; add the notion of max inflight requests to async -- [...truncated 381.03 KB...] kafka.security.auth.ResourceTypeTest >

Build failed in Jenkins: kafka-trunk-jdk9 #174

See Changes: [okaraman] KAFKA-5894; add the notion of max inflight requests to async -- Started by an SCM change [EnvInject] - Loading node environment variables. Building

[jira] [Created] (KAFKA-6179) RecordQueue.clear() does not clear MinTimestampTracker's maintained list

Guozhang Wang created KAFKA-6179: Summary: RecordQueue.clear() does not clear MinTimestampTracker's maintained list Key: KAFKA-6179 URL: https://issues.apache.org/jira/browse/KAFKA-6179 Project:

[GitHub] kafka pull request #3860: KAFKA-5894: add the notion of max inflight request...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3860 ---

Re: [DISCUSS] KIP-220: Add AdminClient into Kafka Streams' ClientSupplier

Hello folks, One update I'd like to propose regarding "compatibility checking": currently we create a single StreamsKafkaClient at the beginning to issue an ApiVersionsRequest to a random broker and then check on its versions, and fail if it does not satisfy the version (0.10.1+ without EOS,

[GitHub] kafka pull request #4185: MINOR: Update Scala 2.11 to 2.11.12

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/4185 MINOR: Update Scala 2.11 to 2.11.12 The main change is Java 9 support. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka scala-2.11.12

Re: [ANNOUNCE] New committer: Onur Karaman

Congrats, Onur! On Mon, Nov 6, 2017 at 2:45 PM, James Cheng wrote: > Congrats Onur! Well deserved! > > -James > > > On Nov 6, 2017, at 9:24 AM, Jun Rao wrote: > > > > Hi, everyone, > > > > The PMC of Apache Kafka is pleased to announce a new Kafka

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

See Changes: [ismael] MINOR: PartitionReassignmentHandler should only generate event when -- [...truncated 382.77 KB...] kafka.security.auth.ResourceTypeTest >

Re: [DISCUSS] KIP-213 Support non-key joining in KTable

It very useful! Thanks a lot! I can follow now whats going on :) One clarification question: Second input is for example key: B0 : value [A2,B0 ...] The second B0 in the value is actually irrelevant, right? The partition key A2B0 is build from B0 from the key, right? -Matthias On 11/6/17

[GitHub] kafka pull request #4085: HOTFIX: poll with zero millis during restoration

Github user guozhangwang closed the pull request at: https://github.com/apache/kafka/pull/4085 ---

Re: [ANNOUNCE] New committer: Onur Karaman

Congrats Onur! Well deserved! -James > On Nov 6, 2017, at 9:24 AM, Jun Rao wrote: > > Hi, everyone, > > The PMC of Apache Kafka is pleased to announce a new Kafka committer Onur > Karaman. > > Onur's most significant work is the improvement of Kafka controller, which > is

[GitHub] kafka pull request #4130: HOTFIX: Remove sysout logging

Github user guozhangwang closed the pull request at: https://github.com/apache/kafka/pull/4130 ---

[GitHub] kafka pull request #4184: MINOR: Remove FanoutIntegrationTest.java

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/4184 MINOR: Remove FanoutIntegrationTest.java This test has been completely subsumed by the coverage of reset integration test, and hence can be removed. You can merge this pull request into a Git

Build failed in Jenkins: kafka-trunk-jdk7 #2950

See Changes: [ismael] MINOR: PartitionReassignmentHandler should only generate event when -- [...truncated 379.91 KB...] kafka.server.DynamicConfigChangeTest >

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

See

Re: [DISCUSS] KIP-222 - Add "describe consumer group" to KafkaAdminClient

Thanks for the feedback! @Ted Yu: Links added. KIP updated. Changes: * `#listConsumerGroups(ListConsumerGroupsOptions options)` added to the API. * `DescribeConsumerGroupResult` and `ConsumerGroupDescription` classes described. Cheers, Jorge. El lun., 6 nov. 2017 a las 20:28, Guozhang Wang

[GitHub] kafka pull request #4183: Kafka 5692 elect preferred

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/4183 Kafka 5692 elect preferred You can merge this pull request into a Git repository by running: $ git pull https://github.com/cmccabe/kafka KAFKA-5692-elect-preferred Alternatively you can

[jira] [Resolved] (KAFKA-6172) Cache lastEntry in TimeIndex to avoid unnecessary disk access

[ https://issues.apache.org/jira/browse/KAFKA-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-6172. - Resolution: Fixed > Cache lastEntry in TimeIndex to avoid unnecessary disk access >

Re: [DISCUSS] 0.11.0.2 bug fix release

There is currently no one assigned to https://issues.apache.org/jira/browse/KAFKA-4972 and https://issues.apache.org/jira/browse/KAFKA-3955. I am not sure either of these has an easy fix. So unless some one picks them up soon, they may need to get moved to the next release. On Mon, Nov 6, 2017 at

Re: [DISCUSS] KIP-213 Support non-key joining in KTable

Going to put all possible szenarios. Just wanted to layout the table and ask if its usefull and understandable first On 06.11.2017 22:33, Ted Yu wrote: bq. Update in A delete in A update in B delete in B Are you going to fill in the above scenario (currently blank) ? On Mon, Nov 6, 2017 at

Build failed in Jenkins: kafka-trunk-jdk9 #173

See Changes: [ismael] MINOR: PartitionReassignmentHandler should only generate event when -- Started by an SCM change [EnvInject] - Loading node environment variables.

Re: [DISCUSS]: KIP-159: Introducing Rich functions to Streams

Hi Matthias, Thanks a lot for correcting. It is a leftover from the past designs when punctuate() was not deprecated. I corrected. Cheers, Jeyhun On Mon, Nov 6, 2017 at 5:30 PM Matthias J. Sax wrote: > I just re-read the KIP. > > One minor comment: we don't need to

[GitHub] kafka pull request #4143: MINOR: PartitionReassignmentHandler should only ge...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4143 ---

Re: [DISCUSS] KIP-219 - Improve Quota Communication

Hi, Jiangjie, 3. If a client closes a socket connection, typically the server only finds this out by reading from the channel and getting a negative size during the read. So, if a channel is muted by the server, the server won't be able to detect the closing of the connection by the client after

Re: [DISCUSS] KIP-213 Support non-key joining in KTable

bq. Update in A delete in A update in B delete in B Are you going to fill in the above scenario (currently blank) ? On Mon, Nov 6, 2017 at 12:31 PM, Jan Filipiak wrote: > I created an example Table in the WIKI page > Can you quickly check if that would be a good

Re: [DISCUSS] 0.11.0.2 bug fix release

Thanks, Guozhang. I will move KAFKA-1923 out of 0.11.0.2. On Mon, Nov 6, 2017 at 5:36 PM, Guozhang Wang wrote: > Thanks Rajini, +1 on releasing a 0.11.0.2. > > I made a pass over the outstanding issues, and added another related issue > ( >

Re: [ANNOUNCE] New committer: Onur Karaman

Congratulations, Onur! On Mon, Nov 6, 2017 at 8:10 PM, Dong Lin wrote: > Congratulations Onur! > > On Mon, Nov 6, 2017 at 9:24 AM, Jun Rao wrote: > > > Hi, everyone, > > > > The PMC of Apache Kafka is pleased to announce a new Kafka committer Onur > >

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

bq. enlarge the score of through() I guess you meant scope. On Mon, Nov 6, 2017 at 1:15 PM, Jeyhun Karimov wrote: > Hi, > > Sorry for the late reply. I am convinced that we should enlarge the score > of through() (add more overloads) instead of introducing a separate set

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

Hi, Sorry for the late reply. I am convinced that we should enlarge the score of through() (add more overloads) instead of introducing a separate set of overloads to other methods. I will update the KIP soon based on the discussion and inform. Cheers, Jeyhun On Mon, Nov 6, 2017 at 9:18 PM Jan

Re: [DISCUSS] KIP-217: Expose a timeout to allow an expired ZK session to be re-created

Ok. Based on the discussion, it seems that doing infinite re-creation is better. I will cancel the KIP. Thanks, Jun On Thu, Nov 2, 2017 at 6:14 PM, Jeff Widman wrote: > +1 for permanent retry under the covers (without an exposed/later > deprecated config). > > That said,

Re: [VOTE] KIP-159: Introducing Rich functions to Streams

Hi Jan, Sorry for late reply. The API Design doesn't look appealing In terms of API design we tried to preserve the java functional interfaces. We applied the same set of rich methods for KTable to make it compatible with the rest of overloaded APIs. It should be 100% sufficient to offer a

[jira] [Created] (KAFKA-6178) Broker is listed as only ISR for all partitions it is leader of

AS created KAFKA-6178: - Summary: Broker is listed as only ISR for all partitions it is leader of Key: KAFKA-6178 URL: https://issues.apache.org/jira/browse/KAFKA-6178 Project: Kafka Issue Type: Bug

Jenkins build is back to normal : kafka-trunk-jdk7 #2949

See

Re: [DISCUSS] KIP-213 Support non-key joining in KTable

I created an example Table in the WIKI page Can you quickly check if that would be a good format? I tried todo it ~like the unit tests but with the information of what state is there _AFTER_ processing happend. I make the first 2 columns exclusive even though the in fact run in parallel but

Re: [DISCUSS] KIP-213 Support non-key joining in KTable

Will do! Need to do it carefully. One mistake in this detailed approach and confusion is perfect ;) Hope I can deliver this week. Best Jan On 06.11.2017 17:21, Matthias J. Sax wrote: Jan, thanks a lot for this KIP. I did an initial pass over it, but feel a little lost. Maybe I need to read

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

Sorry for not beeing 100% up to date. Back then we had the discussion that when an operation puts a >Sink< into the topology, a >Produced< parameter is added. This produced parameter could have internal or external. If internal I think the name would still make a great suffix for the topic

Re: [VOTE] KIP-159: Introducing Rich functions to Streams

Hi. I do understand that it might come in Handy. From my POV in any relational algebra this is only a projection. Currently we hide these "fields" that come with the input record. It should be 100% sufficient to offer a KTable + KStream that is directly feed from a topic with 1 additional

Re: [ANNOUNCE] New committer: Onur Karaman

Congratulations Onur! On Mon, Nov 6, 2017 at 9:24 AM, Jun Rao wrote: > Hi, everyone, > > The PMC of Apache Kafka is pleased to announce a new Kafka committer Onur > Karaman. > > Onur's most significant work is the improvement of Kafka controller, which > is the brain of a

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

See Changes: [rajinisivaram] KAFKA-6156; Metric tag values with colons must be sanitized [becket.qin] KAFKA-6172; Cache lastEntry in TimeIndex to avoid unnecessary disk

Re: [DISCUSS] KIP-222 - Add "describe consumer group" to KafkaAdminClient

Hi Matthias, You meant "list groups" I think? Guozhang On Mon, Nov 6, 2017 at 11:17 AM, Matthias J. Sax wrote: > The main goal of this KIP is to enable decoupling StreamsResetter from > core module. For this case (ie, using AdminClient within > StreamsResetter) we get

Re: [DISCUSS] KIP-222 - Add "describe consumer group" to KafkaAdminClient

Hi Jorge, This looks like a great improvement. I will echo the question that others had about listGroups. Can we just add it to this KIP? It's weird to be able to describe groups, but not list them. In the past, for topics and ACLs, we added describing and listing functionality together. In

Build failed in Jenkins: kafka-trunk-jdk9 #172

See Changes: [wangguoz] KAFKA-6115: TaskManager should be type aware [wangguoz] KAFKA-6120: RecordCollector should not retry sending -- Started by an SCM change

Build failed in Jenkins: kafka-trunk-jdk7 #2948

See Changes: [rajinisivaram] KAFKA-6156; Metric tag values with colons must be sanitized [becket.qin] KAFKA-6172; Cache lastEntry in TimeIndex to avoid unnecessary disk

Re: [DISCUSS] KIP-218: Make KafkaFuture.Function java 8 lambda compatible

It would definitely be nice to use the jdk8 CompletableFuture. I think that's a bit of a separate discussion, though, since it has such heavy compatibility implications. How about making KIP-218 backwards compatible? As a starting point, you can change KafkaFuture#BiConsumer to an interface

Re: [DISCUSS] KIP-222 - Add "describe consumer group" to KafkaAdminClient

The main goal of this KIP is to enable decoupling StreamsResetter from core module. For this case (ie, using AdminClient within StreamsResetter) we get the group.id from the user as command line argument. Thus, I think the KIP is useful without "describe group" command to. I am happy to include

Re: [ANNOUNCE] New committer: Onur Karaman

Congratulations Onur ! -- Edoardo Comar IBM Message Hub IBM UK Ltd, Hursley Park, SO21 2JN From: Jun Rao To: "dev@kafka.apache.org" , "us...@kafka.apache.org" Date:

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

I absolute agree with what you say. It's not a requirement to specify a topic name -- and this was the idea -- if user does specify a name, we treat as is -- if users does not specify a name, Streams create an internal topic. The goal of the Jira is to allow a simplified way to control

Re: [ANNOUNCE] New committer: Onur Karaman

Congratulations Onur ! On Mon, Nov 6, 2017 at 7:01 PM, Matthias J. Sax wrote: > Congrats!!! > > > On 11/6/17 7:56 PM, Vahid S Hashemian wrote: >> Congrats Onur! >> >> --Vahid >> >> >> >> From: Ismael Juma >> To: dev@kafka.apache.org >> Cc:

Re: [ANNOUNCE] New committer: Onur Karaman

Congrats!!! On 11/6/17 7:56 PM, Vahid S Hashemian wrote: > Congrats Onur! > > --Vahid > > > > From: Ismael Juma > To: dev@kafka.apache.org > Cc: "us...@kafka.apache.org" > Date: 11/06/2017 10:13 AM > Subject:Re: [ANNOUNCE] New

Re: [ANNOUNCE] New committer: Onur Karaman

Congrats Onur! --Vahid From: Ismael Juma To: dev@kafka.apache.org Cc: "us...@kafka.apache.org" Date: 11/06/2017 10:13 AM Subject:Re: [ANNOUNCE] New committer: Onur Karaman Sent by:isma...@gmail.com Congratulations

[GitHub] kafka pull request #4148: KAFKA-6120: RecordCollector should not retry sendi...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4148 ---

[GitHub] kafka pull request #4129: KAFKA-6115: TaskManager should be type aware

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4129 ---

Re: kafka-pr-jdk9-scala2.12 keeps failing

Thanks! Ismael On Mon, Nov 6, 2017 at 3:48 AM, Ted Yu wrote: > Logged https://issues.apache.org/jira/browse/INFRA-15448 > > On Thu, Nov 2, 2017 at 11:39 PM, Ismael Juma wrote: > > > This looks to be an issue in Jenkins, not in Kafka. Apache Infra

Re: [ANNOUNCE] New committer: Onur Karaman

Congratulations Onur! Ismael On Mon, Nov 6, 2017 at 5:24 PM, Jun Rao wrote: > Hi, everyone, > > The PMC of Apache Kafka is pleased to announce a new Kafka committer Onur > Karaman. > > Onur's most significant work is the improvement of Kafka controller, which > is the brain

Build failed in Jenkins: kafka-trunk-jdk9 #171

See Changes: [rajinisivaram] KAFKA-6156; Metric tag values with colons must be sanitized [becket.qin] KAFKA-6172; Cache lastEntry in TimeIndex to avoid unnecessary disk

Re: [DISCUSS] KIP-222 - Add "describe consumer group" to KafkaAdminClient

A quick question: I think we do not yet have the `list consumer groups` func as in the old AdminClient. Without this `describe group` given the group id would not be very useful. Could you include this as well in your KIP? More specifically, you can look at kafka.admin.AdminClientfor more details

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

Could you clarify exactly what you mean by keeping the current distinction? Actually, re-reading the KIP and JIRA, it's not clear that being able to specify a custom name is actually a requirement. If the goal is to control repartitioning and tune parallelism, maybe we can just sidestep this

[jira] [Resolved] (KAFKA-1326) New consumer checklist

[ https://issues.apache.org/jira/browse/KAFKA-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-1326. -- Resolution: Fixed > New consumer checklist > -- > > Key:

Re: [DISCUSS] 0.11.0.2 bug fix release

After clicking the outstanding issues link, I only saw KAFKA-6007. Here is the filter in case anyone encounters the same : status in (Open, Reopened, "In Progress", "Patch Available") AND Project = kafka AND fixVersion=0.11.0.2 On Mon, Nov 6, 2017 at 2:47 AM, Rajini Sivaram

Re: [ANNOUNCE] New committer: Onur Karaman

I'd want to add that Onur has also been contributing a lot to the new consumer development in the past, making it happen in the 0.9 release. Very well deserved. Congrats, Onur! Guozhang On Mon, Nov 6, 2017 at 9:28 AM, Ted Yu wrote: > Congratulations, Onur! > > On Mon,

Re: [DISCUSS] 0.11.0.2 bug fix release

Thanks Rajini, +1 on releasing a 0.11.0.2. I made a pass over the outstanding issues, and added another related issue ( https://issues.apache.org/jira/browse/KAFKA-4767) to KAFKA-5936 to the list. For the other outstanding ones that do not yet have assigned to anyone yet, we'd need to start

[GitHub] kafka pull request #4177: KAFKA-6172; Cache lastEntry in TimeIndex to avoid ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4177 ---

Re: [ANNOUNCE] New committer: Onur Karaman

Congratulations, Onur! On Mon, Nov 6, 2017 at 9:24 AM, Jun Rao wrote: > Hi, everyone, > > The PMC of Apache Kafka is pleased to announce a new Kafka committer Onur > Karaman. > > Onur's most significant work is the improvement of Kafka controller, which > is the brain of a

Re: kafka producer : number of record pushed to topic limited

Can you give us some more information ? Were you using a single node setup (127.0.0.1) ? Which release of Kafka are you using ? Anything interesting from broker log ? On Mon, Nov 6, 2017 at 8:52 AM, Dhia Beji wrote: > Hello, > > Would you please help me, I m trying to

[jira] [Created] (KAFKA-6177) kafka-mirror-maker.sh RecordTooLargeException

Rémi REY created KAFKA-6177: --- Summary: kafka-mirror-maker.sh RecordTooLargeException Key: KAFKA-6177 URL: https://issues.apache.org/jira/browse/KAFKA-6177 Project: Kafka Issue Type: Bug

Re: [ANNOUNCE] New committer: Onur Karaman

Congrats Onur! On Mon, Nov 6, 2017 at 9:24 AM, Jun Rao wrote: > Hi, everyone, > > The PMC of Apache Kafka is pleased to announce a new Kafka committer Onur > Karaman. > > Onur's most significant work is the improvement of Kafka controller, which > is the brain of a Kafka

[ANNOUNCE] New committer: Onur Karaman

Hi, everyone, The PMC of Apache Kafka is pleased to announce a new Kafka committer Onur Karaman. Onur's most significant work is the improvement of Kafka controller, which is the brain of a Kafka cluster. Over time, we have accumulated quite a few correctness and performance issues in the

[jira] [Resolved] (KAFKA-6157) Fix repeated words words in JavaDoc and comments.

[ https://issues.apache.org/jira/browse/KAFKA-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-6157. - Resolution: Fixed > Fix repeated words words in JavaDoc and comments. >

kafka producer : number of record pushed to topic limited

Hello, Would you please help me, I m trying to create producer that pushs a large number of json records to topic. Topic creation : kafka-topics --create --zookeeper 127.0.0.1:2181 --replication-factor 1 --partitions 100 --topic testkpa Topic producer :

Re: [VOTE] KIP-159: Introducing Rich functions to Streams

Jan, I understand what you are saying. However, having a RecordContext is super useful for operations that are applied to input topic. Many users requested this feature -- it's much more convenient that falling back to transform() to implement a a filter() for example that want to access some

[GitHub] kafka pull request #4182: KAFKA-6163 fail fast on startup

GitHub user xvrl opened a pull request: https://github.com/apache/kafka/pull/4182 KAFKA-6163 fail fast on startup skip loading remaining logs if we encounter an unrecoverable error on startup @hachikuji @ijuma You can merge this pull request into a Git repository by

Re: [VOTE] KIP-171 - Extend Consumer Group Reset Offset for Stream Application

+1 (binding) Thanks for the KIP, Jorge. Regards, Rajini On Tue, Oct 31, 2017 at 9:58 AM, Damian Guy wrote: > Thanks for the KIP - +1 (binding) > > On Mon, 23 Oct 2017 at 18:39 Guozhang Wang wrote: > > > Thanks Jorge for driving this KIP! +1

Re: [DISCUSS]: KIP-159: Introducing Rich functions to Streams

I just re-read the KIP. One minor comment: we don't need to introduce any deprecated methods. Thus, RichValueTransformer#punctuate can be removed completely instead of introducing it as deprecated. Otherwise looks good to me. Thanks for being so patient! -Matthias On 11/1/17 9:16 PM,

Re: [DISCUSS] KIP-213 Support non-key joining in KTable

Jan, thanks a lot for this KIP. I did an initial pass over it, but feel a little lost. Maybe I need to read it more carefully, but atm it's not clear to me at all what algorithm you propose. I think it would be super helpful, to do an example with concrete data that show how records are stored,

[GitHub] kafka pull request #4173: KAFKA-6156: Metric tag name should not contain col...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4173 ---

[jira] [Resolved] (KAFKA-6156) JmxReporter can't handle windows style directory paths

[ https://issues.apache.org/jira/browse/KAFKA-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-6156. --- Resolution: Fixed Fix Version/s: 1.1.0 Issue resolved by pull request 4173

Re: [DISCUSS] KIP-220: Add AdminClient into Kafka Streams' ClientSupplier

Thanks for the update and clarification. Sounds good to me :) -Matthias On 11/6/17 12:16 AM, Guozhang Wang wrote: > Thanks Matthias, > > 1) Updated the KIP page to include KAFKA-6126. > 2) For passing configs, I agree, will make a pass over the existing configs > passed to

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

That's a good point. In current design, we strictly distinguish both. For example, the reset tools deletes internal topics (starting with prefix `-` and ending with either `-repartition` or `-changelog`. Thus, from my point of view, it would make sense to keep the current distinction. -Matthias

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

I think this sounds good as well. It's worth clarifying whether topics that are named by the user but created by streams are considered "internal" topics also. On Sun, 2017-11-05 at 23:02 +0100, Matthias J. Sax wrote: My idea was, to relax the requirement for through() that a topic must be

Re: [DISCUSS] KIP-219 - Improve Quota Communication

Hi Becket, 2. Perhaps it is fine, though it may be better to limit throttle time to *connections.max.idle.ms* , which is typically a rather large number. 3. The maximum CLOSE_WAIT time is currently bounded by *connections.max.idle.ms

Re: [DISCUSS] KIP-222 - Add "describe consumer group" to KafkaAdminClient

Please fill out Discussion thread and JIRA fields. Thanks On Mon, Nov 6, 2017 at 2:02 AM, Tom Bentley wrote: > Hi Jorge, > > Thanks for the KIP. A few initial comments: > > 1. The AdminClient doesn't have any API like `listConsumerGroups()` > currently, so in general how

Random partitioner for kafka-confluent-dotnet

Hello, We are using confluent-kafka-dotnet 0.9.5. The topic has 50 partitions but when I produce a message with the key as NULL, all the messages are going into the same partition. I looked at Apache's documentation for Kafka and it seems that org.apache.kafka.clients.producer.Partitioner is

[jira] [Created] (KAFKA-6176) numDroppedMessages metric should not be incremented when no data are lost

Daniel Wojda created KAFKA-6176: --- Summary: numDroppedMessages metric should not be incremented when no data are lost Key: KAFKA-6176 URL: https://issues.apache.org/jira/browse/KAFKA-6176 Project: Kafka

[GitHub] kafka pull request #4181: KAFKA-6164: Shutdown quota managers if other compo...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/4181 KAFKA-6164: Shutdown quota managers if other components fail to start You can merge this pull request into a Git repository by running: $ git pull https://github.com/rajinisivaram/kafka

Re: [VOTE] KIP-206: Add support for UUID serialization and deserialization

Hi Ismael, As described in the KIP in Rejected alternatives section - while the string representation is the same on all platforms the binary representation differs. It would be quite easy to add the binary encoding and decoding support to the Java client. But it might make it more complicated to

Re: [VOTE] KIP-206: Add support for UUID serialization and deserialization

non-binding of course On 06.11.2017 12:42, Jan Filipiak wrote: Id Say this is trivial enough for users to implement on their own? -1 I guess On 06.11.2017 10:53, Jakub Scholz wrote: Hi all, Just a friendly reminder that this is still up for vote. If you think this is a good fetrue, please

Re: [VOTE] KIP-206: Add support for UUID serialization and deserialization

Id Say this is trivial enough for users to implement on their own? -1 I guess On 06.11.2017 10:53, Jakub Scholz wrote: Hi all, Just a friendly reminder that this is still up for vote. If you think this is a good fetrue, please give it your vote. Regards Jakub On Tue, Oct 3, 2017 at 11:24

Re: [VOTE] KIP-206: Add support for UUID serialization and deserialization

Thanks for the KIP. It would be good to elaborate a little more on why the binary representation is not suitable. The difference between 16 and 36 bytes is significant. Ismael On Mon, Nov 6, 2017 at 9:53 AM, Jakub Scholz wrote: > Hi all, > > Just a friendly reminder that this

[DISCUSS] 0.11.0.2 bug fix release

Hi all, Since we have fixed some critical issues since 0.11.0.1, it must be time for a 0.11.0.2 release. Since the 0.11.0.1 release we've fixed 14 JIRAs that are targeted for 0.11.0.2:

Re: [DISCUSS] KIP-222 - Add "describe consumer group" to KafkaAdminClient

Hi Jorge, Thanks for the KIP. A few initial comments: 1. The AdminClient doesn't have any API like `listConsumerGroups()` currently, so in general how does a client know the group ids it is interested in? 2. Could you fill in the API of DescribeConsumerGroupResult, just so everyone knows exactly

Re: [VOTE] KIP-206: Add support for UUID serialization and deserialization

Hi all, Just a friendly reminder that this is still up for vote. If you think this is a good fetrue, please give it your vote. Regards Jakub On Tue, Oct 3, 2017 at 11:24 PM, Jakub Scholz wrote: > Hi, > > Since there were no further discussion points, I would like to start the

  1   2   >