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

See Changes: [me] KAFKA-7056: Moved Connect’s new numeric converters to runtime (KIP-305) -- [...truncated 467.68 KB...] kafka.admin.ResetConsumerGroupOffsetTest >

Re: Are defaults serde in Kafka streams doing more harm then good ?

Hi Stephane, The serdes only happen in the following case: 1. when sending to an external topic or repartition topic, this is covered in SinkNode. 2. when reading from external topic, we cover deserialization errors in the DeserializationExceptionHandler interface, customizable in config. 3.

Build failed in Jenkins: kafka-1.0-jdk7 #205

See Changes: [jason] KAFKA-6975; Fix replica fetching from non-batch-aligned log start offset -- [...truncated 1.40 MB...] org.apache.kafka.common.record.MemoryRecordsTest >

[jira] [Resolved] (KAFKA-7056) Connect's new numeric converters should be in a different package

[ https://issues.apache.org/jira/browse/KAFKA-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-7056. -- Resolution: Fixed Fix Version/s: 2.1.0 Issue resolved by pull request

[jira] [Created] (KAFKA-7064) "Unexpected resource type GROUP" when describing broker configs using latest admin client

Rohan Desai created KAFKA-7064: -- Summary: "Unexpected resource type GROUP" when describing broker configs using latest admin client Key: KAFKA-7064 URL: https://issues.apache.org/jira/browse/KAFKA-7064

Jenkins build is back to normal : kafka-trunk-jdk10 #221

See

[jira] [Resolved] (KAFKA-5590) Delete Kafka Topic Complete Failed After Enable Ranger Kafka Plugin

[ https://issues.apache.org/jira/browse/KAFKA-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5590. -- Resolution: Information Provided {color:#00}Closing inactive issue. Please reopen if you think the

[jira] [Resolved] (KAFKA-5691) ZKUtils.CreateRecursive should handle NOAUTH

[ https://issues.apache.org/jira/browse/KAFKA-5691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5691. -- Resolution: Auto Closed Scala consumers and related tools/tests are removed in KAFKA-2983. This change

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

See

[jira] [Resolved] (KAFKA-5408) Using the ConsumerRecord instead of BaseConsumerRecord in the ConsoleConsumer

[ https://issues.apache.org/jira/browse/KAFKA-5408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5408. -- Resolution: Fixed This is taken care in KAFKA-2983 > Using the ConsumerRecord instead of

[jira] [Resolved] (KAFKA-4723) offsets.storage=kafka - groups stuck in rebalancing with committed offsets

[ https://issues.apache.org/jira/browse/KAFKA-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4723. -- Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported. Please

[jira] [Resolved] (KAFKA-4295) kafka-console-consumer.sh does not delete the temporary group in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4295. -- Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported. >

[jira] [Resolved] (KAFKA-4196) Transient test failure: DeleteConsumerGroupTest.testConsumptionOnRecreatedTopicAfterTopicWideDeleteInZK

[ https://issues.apache.org/jira/browse/KAFKA-4196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4196. -- Resolution: Auto Closed Scala consumers and related tools/tests are removed in KAFKA-2983 > Transient

[jira] [Resolved] (KAFKA-3150) kafka.tools.UpdateOffsetsInZK not work (sasl enabled)

[ https://issues.apache.org/jira/browse/KAFKA-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3150. -- Resolution: Auto Closed The Scala consumers and related tools are removed in KAFKA-2983 >

[jira] [Resolved] (KAFKA-3057) "Checking consumer position" docs are referencing (only) deprecated ConsumerOffsetChecker

[ https://issues.apache.org/jira/browse/KAFKA-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3057. -- Resolution: Fixed Closing this as docs updated for kafka-consumer-groups.sh.  documentation about 

[jira] [Resolved] (KAFKA-2584) SecurityProtocol enum validation should be removed or relaxed for non-config usages

[ https://issues.apache.org/jira/browse/KAFKA-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2584. -- Resolution: Auto Closed Closing this as scala clients are deprecated and will be removed in 2.0.0

[jira] [Resolved] (KAFKA-2537) Mirrormaker defaults to localhost with no sanity checks

[ https://issues.apache.org/jira/browse/KAFKA-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2537. -- Resolution: Auto Closed The old consumer is no longer supported. All the usages are removed in 

[jira] [Resolved] (KAFKA-1942) ConsumerGroupCommand does not show offset information in ZK for deleted topic

[ https://issues.apache.org/jira/browse/KAFKA-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1942. -- Resolution: Auto Closed Closing as old consumer support is removed from ConsumerGroupCommand >

Jenkins build is back to normal : kafka-0.10.2-jdk7 #215

See

[jira] [Resolved] (KAFKA-857) kafka.admin.ListTopicCommand, 'by broker' display/filter

[ https://issues.apache.org/jira/browse/KAFKA-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-857. - Resolution: Auto Closed Closing inactive issue.  This functionality can be achived by using

Build failed in Jenkins: kafka-trunk-jdk10 #220

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H30 (ubuntu xenial) in workspace

[jira] [Resolved] (KAFKA-796) Kafka Scala classes should declare thrown checked exceptions to be Java friendly

[ https://issues.apache.org/jira/browse/KAFKA-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-796. - Resolution: Auto Closed Closing inactive issue. The scala clients are no longer supported. > Kafka Scala

Build failed in Jenkins: kafka-trunk-jdk10 #219

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H30 (ubuntu xenial) in workspace

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

I think this makes perfect sense. Thanks for opening this KIP. Thanks & Regards Jakub On Fri, Jun 15, 2018 at 2:10 AM Kevin Lafferty wrote: > Hi all, > > I created KIP-316, and I would like to initiate discussion. > > The KIP is here: > >

[jira] [Resolved] (KAFKA-3798) Kafka Consumer 0.10.0.0 killed after rebalancing exception

[ https://issues.apache.org/jira/browse/KAFKA-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3798. -- Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported. Please

[jira] [Resolved] (KAFKA-4967) java.io.EOFException Error while committing offsets

[ https://issues.apache.org/jira/browse/KAFKA-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4967. -- Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported. Please

[jira] [Resolved] (KAFKA-966) Allow high level consumer to 'nak' a message and force Kafka to close the KafkaStream without losing that message

[ https://issues.apache.org/jira/browse/KAFKA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-966. - Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported.  > Allow high

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

Change looks good. Thanks On Fri, Jun 15, 2018 at 8:42 AM, Lucas Wang wrote: > Hi Ted, > > Thanks for the suggestion. I've updated the KIP. Please take another look. > > Lucas > > On Thu, Jun 14, 2018 at 6:34 PM, Ted Yu wrote: > > > Currently in KafkaConfig.scala : > > > > val

[jira] [Resolved] (KAFKA-2546) CPU utilization very high when no kafka node alive

[ https://issues.apache.org/jira/browse/KAFKA-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2546. -- Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported. Please

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

Hi Ted, Thanks for the suggestion. I've updated the KIP. Please take another look. Lucas On Thu, Jun 14, 2018 at 6:34 PM, Ted Yu wrote: > Currently in KafkaConfig.scala : > > val QueuedMaxRequests = 500 > > It would be good if you can include the default value for this new config > in the

[jira] [Resolved] (KAFKA-7021) Source KTable checkpoint is not correct

[ https://issues.apache.org/jira/browse/KAFKA-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-7021. -- Resolution: Fixed > Source KTable checkpoint is not correct >

[jira] [Created] (KAFKA-7063) Update documentation to remove references to old producers and consumers

Ismael Juma created KAFKA-7063: -- Summary: Update documentation to remove references to old producers and consumers Key: KAFKA-7063 URL: https://issues.apache.org/jira/browse/KAFKA-7063 Project: Kafka

[jira] [Created] (KAFKA-7062) Simplify MirrorMaker loop after removal of old consumer support

Ismael Juma created KAFKA-7062: -- Summary: Simplify MirrorMaker loop after removal of old consumer support Key: KAFKA-7062 URL: https://issues.apache.org/jira/browse/KAFKA-7062 Project: Kafka

Jenkins build is back to normal : kafka-trunk-jdk10 #218

See

Error in Kafka Stream

Hi, I am getting the below error while processign data with kafka stream. The application was runnign for a couple of hours and the ' WatchlistUpdate-StreamThread-9 ' thread was assigned to the same partition since beginning. I am assuming it was able to successfully commit offsets for those

Build failed in Jenkins: kafka-trunk-jdk10 #217

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H30 (ubuntu xenial) in workspace

Re: [VOTE] KIP-280: Enhanced log compaction

If selection exists in header, the selection should override the config value. Cheers Original message From: Luis Cabral Date: 6/15/18 1:40 AM (GMT-08:00) To: dev@kafka.apache.org Subject: Re: [VOTE] KIP-280: Enhanced log compaction Hi, bq. Can the value be determined now ?

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

See Changes: [matthias] KAFKA-6360: Clear RocksDB Segments when store is closed -- [...truncated 1.30 MB...]

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

Hey Kevin, I am not yet a committer so my word doesn't hold much weight but to me this is a no-brainer of a decision - this KIP can only improve the cli tool +1 From: Kevin Lafferty Sent: Friday, 15 June 2018 3:10 To: dev@kafka.apache.org Subject: [DISCUSS]

Re: [VOTE] KIP-280: Enhanced log compaction

Hi, bq. Can the value be determined now ? My thinking is that what if there is a third compaction strategy proposed in the future ? We should guard against user unknowingly choosing the 'future' strategy. The idea is that the header name to use is flexible, which protects current clients that

Build failed in Jenkins: kafka-trunk-jdk10 #216

See Changes: [jason] MINOR: Fix chunked down-conversion behavior when no valid batch exists -- [...truncated 1.57 MB...] kafka.security.auth.ResourceTest >

[jira] [Created] (KAFKA-7061) Enhanced log compaction

Luis Cabral created KAFKA-7061: -- Summary: Enhanced log compaction Key: KAFKA-7061 URL: https://issues.apache.org/jira/browse/KAFKA-7061 Project: Kafka Issue Type: Improvement

Jenkins build is back to normal : kafka-0.11.0-jdk7 #380

See