[jira] [Created] (KAFKA-6632) Very slow hashCode methods in Kafka Connect types

Maciej Bryński created KAFKA-6632: - Summary: Very slow hashCode methods in Kafka Connect types Key: KAFKA-6632 URL: https://issues.apache.org/jira/browse/KAFKA-6632 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-6535) Set default retention ms for Streams repartition topics to infinity

[ https://issues.apache.org/jira/browse/KAFKA-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392692#comment-16392692 ] Khaireddine Rezgui commented on KAFKA-6535: --- Infinity == Integer.MAX_VALUE ? [~

[jira] [Created] (KAFKA-6633) Is KafkaProducer still thread safe in version 1.0.1

Herbert Koelman created KAFKA-6633: -- Summary: Is KafkaProducer still thread safe in version 1.0.1 Key: KAFKA-6633 URL: https://issues.apache.org/jira/browse/KAFKA-6633 Project: Kafka Issue T

[jira] [Commented] (KAFKA-6633) Is KafkaProducer still thread safe in version 1.0.1

[ https://issues.apache.org/jira/browse/KAFKA-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392763#comment-16392763 ] Mickael Maison commented on KAFKA-6633: --- Yes it is still the case. And it's also sti

[jira] [Resolved] (KAFKA-6633) Is KafkaProducer still thread safe in version 1.0.1

[ https://issues.apache.org/jira/browse/KAFKA-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-6633. --- Resolution: Not A Problem > Is KafkaProducer still thread safe in version 1.0.1 >

[jira] [Updated] (KAFKA-6632) Very slow hashCode methods in Kafka Connect types

[ https://issues.apache.org/jira/browse/KAFKA-6632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maciej Bryński updated KAFKA-6632: -- Description: hashCode method of ConnectSchema (and Field) is used a lot in SMT and fromConnect.

[jira] [Commented] (KAFKA-6632) Very slow hashCode methods in Kafka Connect types

[ https://issues.apache.org/jira/browse/KAFKA-6632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392790#comment-16392790 ] Maciej Bryński commented on KAFKA-6632: --- I checked also Struct Schemas. My implemen

[jira] [Commented] (KAFKA-6633) Is KafkaProducer still thread safe in version 1.0.1

[ https://issues.apache.org/jira/browse/KAFKA-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392845#comment-16392845 ] Herbert Koelman commented on KAFKA-6633: Thanks for this quick answear. > Is Kafk

[jira] [Closed] (KAFKA-6633) Is KafkaProducer still thread safe in version 1.0.1

[ https://issues.apache.org/jira/browse/KAFKA-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herbert Koelman closed KAFKA-6633. -- > Is KafkaProducer still thread safe in version 1.0.1 >

[jira] [Updated] (KAFKA-5863) Potential null dereference in DistributedHerder#reconfigureConnector()

[ https://issues.apache.org/jira/browse/KAFKA-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KAFKA-5863: -- Description: Here is the call chain: {code} RestServer.httpRequest(reconfigUrl,

[jira] [Commented] (KAFKA-6399) Consider reducing "max.poll.interval.ms" default for Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393169#comment-16393169 ] Bill Bejeck commented on KAFKA-6399: I'm +1 as well for reducing the {{max.poll.interv

[jira] [Commented] (KAFKA-6626) Performance bottleneck in Kafka Connect sendRecords

[ https://issues.apache.org/jira/browse/KAFKA-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393217#comment-16393217 ] Ewen Cheslack-Postava commented on KAFKA-6626: -- It cannot be a regular map, s

[jira] [Commented] (KAFKA-6474) Rewrite test to use new public TopologyTestDriver

[ https://issues.apache.org/jira/browse/KAFKA-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393415#comment-16393415 ] John Roesler commented on KAFKA-6474: - Hi Filipe, I have been working on a similar ta

[jira] [Commented] (KAFKA-6474) Rewrite test to use new public TopologyTestDriver

[ https://issues.apache.org/jira/browse/KAFKA-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393444#comment-16393444 ] John Roesler commented on KAFKA-6474: - Also worth mentioning is [~guozhang]'s reply: {

[jira] [Commented] (KAFKA-6535) Set default retention ms for Streams repartition topics to infinity

[ https://issues.apache.org/jira/browse/KAFKA-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393457#comment-16393457 ] Matthias J. Sax commented on KAFKA-6535: Yes. It's a long though (not and integer)

[jira] [Commented] (KAFKA-6399) Consider reducing "max.poll.interval.ms" default for Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393486#comment-16393486 ] Matthias J. Sax commented on KAFKA-6399: Thanks for the feedback. It's a tricky qu

[jira] [Assigned] (KAFKA-6627) Console producer default config values override explicitly provided properties

[ https://issues.apache.org/jira/browse/KAFKA-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Murakozi reassigned KAFKA-6627: -- Assignee: Sandor Murakozi > Console producer default config values override explicitly

[jira] [Commented] (KAFKA-6535) Set default retention ms for Streams repartition topics to infinity

[ https://issues.apache.org/jira/browse/KAFKA-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393587#comment-16393587 ] John Roesler commented on KAFKA-6535: - I don't think it's that important in this conte

[jira] [Commented] (KAFKA-6631) Kafka Streams - Rebalancing exception in Kafka 1.0.0

[ https://issues.apache.org/jira/browse/KAFKA-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393680#comment-16393680 ] Guozhang Wang commented on KAFKA-6631: -- Hello Alexander, Thanks for reporting this i

[jira] [Commented] (KAFKA-6622) GroupMetadataManager.loadGroupsAndOffsets decompresses record batch needlessly

[ https://issues.apache.org/jira/browse/KAFKA-6622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393695#comment-16393695 ] ASF GitHub Bot commented on KAFKA-6622: --- hachikuji closed pull request #4661: KAFKA-

[jira] [Resolved] (KAFKA-6622) GroupMetadataManager.loadGroupsAndOffsets decompresses record batch needlessly

[ https://issues.apache.org/jira/browse/KAFKA-6622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6622. Resolution: Fixed Fix Version/s: 1.1.0 > GroupMetadataManager.loadGroupsAndOffsets de

[jira] [Assigned] (KAFKA-6264) Log cleaner thread may die on legacy segment containing messages whose offsets are too large

[ https://issues.apache.org/jira/browse/KAFKA-6264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhruvil Shah reassigned KAFKA-6264: --- Assignee: Dhruvil Shah (was: Jiangjie Qin) > Log cleaner thread may die on legacy segment co

[jira] [Created] (KAFKA-6634) Delay initiating the txn on producers until initializeTopology with EOS turned on

Guozhang Wang created KAFKA-6634: Summary: Delay initiating the txn on producers until initializeTopology with EOS turned on Key: KAFKA-6634 URL: https://issues.apache.org/jira/browse/KAFKA-6634 Proje

[jira] [Comment Edited] (KAFKA-5846) Use singleton NoOpConsumerRebalanceListener in subscribe() call where listener is not specified

[ https://issues.apache.org/jira/browse/KAFKA-5846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191405#comment-16191405 ] Ted Yu edited comment on KAFKA-5846 at 3/10/18 12:42 AM: - Patch lo