[jira] [Created] (KAFKA-7665) Replace BaseConsumerRecord with ConsumerRecord in MM

huxihx created KAFKA-7665: - Summary: Replace BaseConsumerRecord with ConsumerRecord in MM Key: KAFKA-7665 URL: https://issues.apache.org/jira/browse/KAFKA-7665 Project: Kafka Issue Type: Improvement

Jenkins build is back to normal : kafka-2.1-jdk8 #59

See

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

See

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

See Changes: [github] KAFKA-7536: Initialize TopologyTestDriver with non-null topic (#5923) -- [...truncated 2.38 MB...]

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

See Changes: [lindong28] Bump version to 2.1.0 [lindong28] MINOR: Update version numbers to 2.1.1-SNAPSHOT -- [...truncated 2.62 MB...]

[jira] [Resolved] (KAFKA-7528) Standardize on Min/Avg/Max Kafka metrics' default value

[ https://issues.apache.org/jira/browse/KAFKA-7528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-7528. -- Resolution: Fixed > Standardize on Min/Avg/Max Kafka metrics' default value >

Re: [DISCUSS] KIP-345: Reduce multiple consumer rebalances by specifying member id

Hi Boyang, Thanks for updating the KIP. This is a step good direction for stateful applications and also mirroring applications whose latency is affected due to the rebalance issues that we have today. I had a few questions on the current version of the KIP : For the effectiveness of the KIP,

Re: [DISCUSS] KIP-345: Reduce multiple consumer rebalances by specifying member id

Thanks Konstantine for correcting the details within proposal for me! Addressed them below: > In a few places the new/proposed changes are referred to as "current". > Which is a bit confusing considering that there is a protocol in place > already, and by "current" someone might understand the

[jira] [Resolved] (KAFKA-7536) TopologyTestDriver cannot pre-populate KTable or GlobalKTable

[ https://issues.apache.org/jira/browse/KAFKA-7536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-7536. -- Resolution: Fixed Assignee: Guozhang Wang Fix Version/s: 2.0.2

Re: [DISCUSS] KIP-258: Allow to Store Record Timestamps in RocksDB

It's an interesting idea to use second store, to maintain the timestamps. However, each RocksDB instance implies some overhead. In fact, we are looking into ColumnFamilies atm to see if we can use those and merge multiple RocksDBs into a single one to reduce this overhead. -Matthias On 11/20/18

Re: Need to subscribe to mail list and get access to contribute to jira tickets

Mailing list subscription is self-service: https://kafka.apache.org/contact On 11/20/18 8:39 AM, Manikumar wrote: > Hi, > > I have given JIRA permissions for "kaushik srinivas" JIRA username. > > On Tue, Nov 20, 2018 at 3:29 PM KAUSHIK SRINIVAS < > kaushiksrinivas...@gmail.com> wrote: > >> Hi,

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

See

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

See Changes: [manikumar.reddy] KAFKA-7616; Make MockConsumer only add entries to the partition map -- [...truncated 2.63 MB...]

[jira] [Resolved] (KAFKA-7577) Semantics of Table-Table Join with Null Message Are Incorrect

[ https://issues.apache.org/jira/browse/KAFKA-7577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daren Thomas resolved KAFKA-7577. - Resolution: Not A Problem > Semantics of Table-Table Join with Null Message Are Incorrect >

RE: [EXTERNAL] - Re: [DISCUSS] KIP-387: Fair Message Consumption Across Partitions in KafkaConsumer

Hi Matt, Thanks for the feedback. The issue with the current design is that it stays on the previous partition even if the last poll call consumes the max.poll.records; it will consume all records in that partition available at the consumer side to serve multiple poll calls before moving to

[RESULTS] [VOTE] Release Kafka version 2.1.0

This vote passes with 10 +1 votes (3 bindings) and no 0 or -1 votes. +1 votes PMC Members: * Guozhang Wang * Jason Gustafson * Dong Lin Committers: * Vahid Hashemian * ManiKumar Reddy Community: * Jonathan Santilli * Eno Thereska * Andras Beni * Jakub Scholz * Satish Duggana 0 votes *

[jira] [Resolved] (KAFKA-6971) Passing in help flag to kafka-console-producer should print arg options

[ https://issues.apache.org/jira/browse/KAFKA-6971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6971. -- Resolution: Duplicate > Passing in help flag to kafka-console-producer should print arg options >

Re: [DISCUSS] KIP-345: Reduce multiple consumer rebalances by specifying member id

Hi Boyang. Thanks for preparing this KIP! It is making good progress and will be a great improvement for stateful Kafka applications. Apologies for my late reply, I was away for a while. Lots of great comments so far, so I'll probably second most of them in what I suggest below at this point.

Re: [VOTE] 2.1.0 RC1

Thanks everyone for your test and vote! We have removed those unnecessary files (as Ismael mentioned) from the staging repository and this release has collected enough votes. I will continue with the release process. On Tue, Nov 20, 2018 at 12:08 AM Jason Gustafson wrote: > +1 > > I verified

[jira] [Created] (KAFKA-7664) Docs kafka.apache.org does not include CLI to re-assign replicas between disks of the same broker

Sudarshan Pathalam created KAFKA-7664: - Summary: Docs kafka.apache.org does not include CLI to re-assign replicas between disks of the same broker Key: KAFKA-7664 URL:

[jira] [Resolved] (KAFKA-7616) MockConsumer can return ConsumerRecords objects with a non-empty map but no records

[ https://issues.apache.org/jira/browse/KAFKA-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7616. -- Resolution: Fixed Fix Version/s: 2.2.0 Issue resolved by pull request 5901

[jira] [Created] (KAFKA-7663) Custom Processor supplied on addGlobalStore is not used when restoring state from topic

Frederic Tardif created KAFKA-7663: -- Summary: Custom Processor supplied on addGlobalStore is not used when restoring state from topic Key: KAFKA-7663 URL: https://issues.apache.org/jira/browse/KAFKA-7663

[jira] [Resolved] (KAFKA-7659) dummy test

[ https://issues.apache.org/jira/browse/KAFKA-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7659. -- Resolution: Invalid > dummy test > -- > > Key: KAFKA-7659 >

Re: Need to subscribe to mail list and get access to contribute to jira tickets

Hi, I have given JIRA permissions for "kaushik srinivas" JIRA username. On Tue, Nov 20, 2018 at 3:29 PM KAUSHIK SRINIVAS < kaushiksrinivas...@gmail.com> wrote: > Hi, > > Need subscription to kafka mailing list. > > Also need to assign jira tickets to myself. Have worked on few pull > requests

[jira] [Created] (KAFKA-7662) Avro schema upgrade not supported on globalTable

Frederic Tardif created KAFKA-7662: -- Summary: Avro schema upgrade not supported on globalTable Key: KAFKA-7662 URL: https://issues.apache.org/jira/browse/KAFKA-7662 Project: Kafka Issue

"version" in kafka-reassign-partitions's JSON input file is not updated by KIP-113

Hi there, KIP-113 added a new, optional filed to the input JSON file of kafka-reassign-partitions: { "version" : int, "partitions" : [ { "topic" : str, "partition" : int, "replicas" : [int], "log_dirs" : [str]<-- NEW. A log directory can be either "any", or a

[DISCUSS] KIP-375 Kafka Clients - make Metadata#TOPIC_EXPIRY_MS configurable

Hello https://cwiki.apache.org/confluence/display/KAFKA/KIP-375%3A+Kafka+Clients+-+make+Metadata%23TOPIC_EXPIRY_MS+configurable I'd like to introduce new feature for kafka client: Making org.apache.kafka.clients.Metadata#TOPIC_EXPIRY_MS configurable Here is KPI

[jira] [Reopened] (KAFKA-7565) NPE in KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-7565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-7565: > NPE in KafkaConsumer > > > Key: KAFKA-7565 >

Re: [Discuss] KIP-389: Enforce group.max.size to cap member metadata growth

Hey there everybody, Thanks for the introduction Boyang. I appreciate the effort you are putting into improving consumer behavior in Kafka. @Matt I also believe the default value is high. In my opinion, we should aim to a default cap around 250. This is because in the current model any consumer

[jira] [Created] (KAFKA-7661) Upgrade compatibility matrix

Pavel Kozlov created KAFKA-7661: --- Summary: Upgrade compatibility matrix Key: KAFKA-7661 URL: https://issues.apache.org/jira/browse/KAFKA-7661 Project: Kafka Issue Type: Improvement

Re: [DISCUSS] KIP-258: Allow to Store Record Timestamps in RocksDB

Hi Adam Sounds great, I was already planning to ask around if anyone had tackled this. We have a use case very similar to what you described in KAFKA-4212, only with Global State Stores. I have tried a few things with the normal DSL but was not really successful. Schedule/Punctuate is not

Re: [DISCUSS] KIP-345: Reduce multiple consumer rebalances by specifying member id

Thanks Guozhang for the great summary here, and I have been following up the action items here. 1. I already updated the KIP to remove the expansion timeout and registration timeout. Great to see them being addressed in client side! 2. I double checked the design and I believe that it is

[jira] [Created] (KAFKA-7660) Stream Metrics - Memory Analysis

Patrik Kleindl created KAFKA-7660: - Summary: Stream Metrics - Memory Analysis Key: KAFKA-7660 URL: https://issues.apache.org/jira/browse/KAFKA-7660 Project: Kafka Issue Type: Bug

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

See Changes: [manikumar.reddy] MINOR: Improve maven artifactory url in release.py (#5931) -- [...truncated 2.25 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Re: [Discuss] KIP-389: Enforce group.max.size to cap member metadata growth

Thanks Matt for the suggestion! I'm still open to any suggestion to change the default value. Meanwhile I just want to point out that this value is a just last line of defense, not a real scenario we would expect. In the meanwhile, I discussed with Stanislav and he would be driving the 389

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

See Changes: [manikumar.reddy] MINOR: Improve maven artifactory url in release.py (#5931) -- [...truncated 2.63 MB...] org.apache.kafka.connect.transforms.CastTest >

Need to subscribe to mail list and get access to contribute to jira tickets

Hi, Need subscription to kafka mailing list. Also need to assign jira tickets to myself. Have worked on few pull requests and need to submit the code. Need support in getting the required permissions to assign the kafka jira ticket to myself. Thanks & Regards, kaushik

[jira] [Created] (KAFKA-7659) dummy test

kaushik srinivas created KAFKA-7659: --- Summary: dummy test Key: KAFKA-7659 URL: https://issues.apache.org/jira/browse/KAFKA-7659 Project: Kafka Issue Type: Improvement Components:

Re: Request for permissions to add KIP for user shnguyen

Hello Shawn, I should have already added you 4 days ago when replying to this thread, could you try again? Guozhang On Mon, Nov 19, 2018 at 8:47 PM Shawn Nguyen wrote: > Hey folks, > Any chance I could get permissions to add a KIP > < >

Re: [DISCUSS] KIP-345: Reduce multiple consumer rebalances by specifying member id

Hello Boyang, Thanks a lot for the KIP! It is a great write-up and I appreciate your patience answering to the feedbacks from the community. I'd like to add my 2cents here: 1. By introducing another two timeout configs, registration_timeout and expansion_timeout, we are effectively having four

Re: [VOTE] 2.1.0 RC1

+1 I verified the release and upgrade notes. I also went through the basic quickstart. Great job running the release, Dong! Thanks for all the effort. -Jason On Mon, Nov 19, 2018 at 10:50 AM, Dong Lin wrote: > Hey Ismael, > > I checked out a clean copy of Kafka and reuploaded artifacts for

Re: [DISCUSS] KIP-258: Allow to Store Record Timestamps in RocksDB

I did not think about how TTL should be integrated exactly. However, it seems reasonable, to provide TTL not based on RocksDB built-in TTL, because we want to synchronize deletes in RocksDB with deletes in the changelog topic (to avoid the filtering you implemented). Thus, on each put() we could