[jira] [Created] (KAFKA-7686) Remove PowerMock from Connect Tests

Magesh kumar Nandakumar created KAFKA-7686: -- Summary: Remove PowerMock from Connect Tests Key: KAFKA-7686 URL: https://issues.apache.org/jira/browse/KAFKA-7686 Project: Kafka Issue T

[jira] [Commented] (KAFKA-4212) Add a key-value store that is a TTL persistent cache

[ https://issues.apache.org/jira/browse/KAFKA-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702657#comment-16702657 ] Guozhang Wang commented on KAFKA-4212: -- cc [~mjsax], I think you are already aware b

[jira] [Commented] (KAFKA-7566) Add sidecar job to leader (or a random single follower) only

[ https://issues.apache.org/jira/browse/KAFKA-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702656#comment-16702656 ] Guozhang Wang commented on KAFKA-7566: -- Were you triggering this job via the punctua

[jira] [Commented] (KAFKA-7678) Failed to close producer due to java.lang.NullPointerException

[ https://issues.apache.org/jira/browse/KAFKA-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702652#comment-16702652 ] Guozhang Wang commented on KAFKA-7678: -- Looked at the source code, and I think it is

[jira] [Commented] (KAFKA-7449) Kafka console consumer is not sending topic to deserializer

[ https://issues.apache.org/jira/browse/KAFKA-7449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702633#comment-16702633 ] ASF GitHub Bot commented on KAFKA-7449: --- junrao closed pull request #5704: KAFKA-74

[jira] [Resolved] (KAFKA-7449) Kafka console consumer is not sending topic to deserializer

[ https://issues.apache.org/jira/browse/KAFKA-7449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-7449. Resolution: Fixed Assignee: Mathieu Chataigner Fix Version/s: 2.2.0 Merged to trunk. > Kaf

[jira] [Commented] (KAFKA-7671) A KStream/GlobalKTable join shouldn't reset the repartition flag

[ https://issues.apache.org/jira/browse/KAFKA-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702630#comment-16702630 ] ASF GitHub Bot commented on KAFKA-7671: --- guozhangwang closed pull request #5959: KA

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

[ https://issues.apache.org/jira/browse/KAFKA-7660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrik Kleindl updated KAFKA-7660: -- Attachment: heapdump-1543441898901.hprof > Stream Metrics - Memory Analysis > -

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

[ https://issues.apache.org/jira/browse/KAFKA-7660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702422#comment-16702422 ] Patrik Kleindl commented on KAFKA-7660: --- [~vvcephei] Well, at least that answers my

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

[ https://issues.apache.org/jira/browse/KAFKA-7660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702387#comment-16702387 ] John Roesler commented on KAFKA-7660: - [~pkleindl], Ah, yes, now I'm remembering why

[jira] [Issue Comment Deleted] (KAFKA-6988) Kafka windows classpath too long

[ https://issues.apache.org/jira/browse/KAFKA-6988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lkgen updated KAFKA-6988: - Comment: was deleted (was: retest this please) > Kafka windows classpath too long >

[jira] [Commented] (KAFKA-6988) Kafka windows classpath too long

[ https://issues.apache.org/jira/browse/KAFKA-6988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702333#comment-16702333 ] lkgen commented on KAFKA-6988: -- retest this please > Kafka windows classpath too long > ---

[jira] [Commented] (KAFKA-7682) turning on request logging for a subset of request types

[ https://issues.apache.org/jira/browse/KAFKA-7682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702304#comment-16702304 ] Gwen Shapira commented on KAFKA-7682: - To add to the future KIP discussion: In additi

[jira] [Commented] (KAFKA-7669) Stream topology definition is not robust to the ordering changes

[ https://issues.apache.org/jira/browse/KAFKA-7669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702291#comment-16702291 ] Guozhang Wang commented on KAFKA-7669: -- [~nijo] Also note that there is another KIP

[jira] [Commented] (KAFKA-7654) Relax requirements on serializing-only methods.

[ https://issues.apache.org/jira/browse/KAFKA-7654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702279#comment-16702279 ] Guozhang Wang commented on KAFKA-7654: -- For 3), the main caveat is because of Java's

[jira] [Commented] (KAFKA-7610) Detect consumer failures in initial JoinGroup

[ https://issues.apache.org/jira/browse/KAFKA-7610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702277#comment-16702277 ] ASF GitHub Bot commented on KAFKA-7610: --- hachikuji opened a new pull request #5962:

[jira] [Commented] (KAFKA-5581) Avoid creating changelog topics for state stores that are materialized from a source topic

[ https://issues.apache.org/jira/browse/KAFKA-5581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702274#comment-16702274 ] Guozhang Wang commented on KAFKA-5581: -- 1) I agree that there are gotchas with this

[jira] [Commented] (KAFKA-7678) Failed to close producer due to java.lang.NullPointerException

[ https://issues.apache.org/jira/browse/KAFKA-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702239#comment-16702239 ] Matthias J. Sax commented on KAFKA-7678: Thank you! > Failed to close producer d

[jira] [Commented] (KAFKA-6951) Implement offset expiration semantics for unsubscribed topics

[ https://issues.apache.org/jira/browse/KAFKA-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702167#comment-16702167 ] James Cheng commented on KAFKA-6951: [~vultron81]: I think that the kafka-consumer-gr

[jira] [Commented] (KAFKA-7681) new metric for request thread utilization by request type

[ https://issues.apache.org/jira/browse/KAFKA-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702176#comment-16702176 ] Jun Rao commented on KAFKA-7681: Hi, [~mgharat], The Broker Topic metrics only collect t

[jira] [Updated] (KAFKA-6988) Kafka windows classpath too long

[ https://issues.apache.org/jira/browse/KAFKA-6988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lkgen updated KAFKA-6988: - Affects Version/s: 2.0.0 > Kafka windows classpath too long > > >

[jira] [Commented] (KAFKA-6988) Kafka windows classpath too long

[ https://issues.apache.org/jira/browse/KAFKA-6988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702137#comment-16702137 ] ASF GitHub Bot commented on KAFKA-6988: --- lkgendev opened a new pull request #5960:

[jira] [Assigned] (KAFKA-7671) A KStream/GlobalKTable join shouldn't reset the repartition flag

[ https://issues.apache.org/jira/browse/KAFKA-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck reassigned KAFKA-7671: -- Assignee: Bill Bejeck > A KStream/GlobalKTable join shouldn't reset the repartition flag > ---

[jira] [Commented] (KAFKA-7671) A KStream/GlobalKTable join shouldn't reset the repartition flag

[ https://issues.apache.org/jira/browse/KAFKA-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702045#comment-16702045 ] ASF GitHub Bot commented on KAFKA-7671: --- bbejeck opened a new pull request #5959: K

[jira] [Commented] (KAFKA-2607) Review `Time` interface and its usage

[ https://issues.apache.org/jira/browse/KAFKA-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701980#comment-16701980 ] ASF GitHub Bot commented on KAFKA-2607: --- Al12 opened a new pull request #5958: KAFK

[jira] [Commented] (KAFKA-6951) Implement offset expiration semantics for unsubscribed topics

[ https://issues.apache.org/jira/browse/KAFKA-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701872#comment-16701872 ] Ben Williams commented on KAFKA-6951: - Is there no way for a topic to expire or be un

[jira] [Created] (KAFKA-7685) Support loading trust stores from classpath

Noa Resare created KAFKA-7685: - Summary: Support loading trust stores from classpath Key: KAFKA-7685 URL: https://issues.apache.org/jira/browse/KAFKA-7685 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-7641) Add `consumer.group.max.size` to cap consumer metadata size on broker

[ https://issues.apache.org/jira/browse/KAFKA-7641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701746#comment-16701746 ] Justin Jack commented on KAFKA-7641: oka good and sorry for disturbing you > Add `co

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

[ https://issues.apache.org/jira/browse/KAFKA-7660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701743#comment-16701743 ] Patrik Kleindl commented on KAFKA-7660: --- [~vvcephei] Hi John I tried applying the

[jira] [Commented] (KAFKA-7641) Add `consumer.group.max.size` to cap consumer metadata size on broker

[ https://issues.apache.org/jira/browse/KAFKA-7641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701741#comment-16701741 ] Stanislav Kozlovski commented on KAFKA-7641: Hi Jack, Thanks for offering hel

[jira] [Commented] (KAFKA-7641) Add `consumer.group.max.size` to cap consumer metadata size on broker

[ https://issues.apache.org/jira/browse/KAFKA-7641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701703#comment-16701703 ] Justin Jack commented on KAFKA-7641: This change will require a KIP as it is a public

[jira] [Commented] (KAFKA-7037) delete topic command replaces '+' from the topic name which leads incorrect topic deletion

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

[jira] [Commented] (KAFKA-7678) Failed to close producer due to java.lang.NullPointerException

[ https://issues.apache.org/jira/browse/KAFKA-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701647#comment-16701647 ] Jonathan Santilli commented on KAFKA-7678: -- Yes [~mjsax] , is like that, still f

[jira] [Assigned] (KAFKA-7678) Failed to close producer due to java.lang.NullPointerException

[ https://issues.apache.org/jira/browse/KAFKA-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Santilli reassigned KAFKA-7678: Assignee: Jonathan Santilli > Failed to close producer due to java.lang.NullPointe

[jira] [Updated] (KAFKA-7678) Failed to close producer due to java.lang.NullPointerException

[ https://issues.apache.org/jira/browse/KAFKA-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Santilli updated KAFKA-7678: - Priority: Minor (was: Major) > Failed to close producer due to java.lang.NullPointerExce

[jira] [Resolved] (KAFKA-6149) LogCleanerManager should include topic partition name when warning of invalid cleaner offset

[ https://issues.apache.org/jira/browse/KAFKA-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6149. -- Resolution: Fixed Fix Version/s: 0.11.0.1 1.0.0 This was fixed in 1.0 and 0.1

[jira] [Commented] (KAFKA-7679) With acks=all a single "stuck" non-leader replica can cause a timeout

[ https://issues.apache.org/jira/browse/KAFKA-7679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701568#comment-16701568 ] Ismael Juma commented on KAFKA-7679: I think there's a misunderstanding of the curren

[jira] [Updated] (KAFKA-7679) With acks=all a single "stuck" non-leader replica can cause a timeout

[ https://issues.apache.org/jira/browse/KAFKA-7679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Corentin Chary updated KAFKA-7679: -- Description: >From the documentation: {code:java} acks=all This means the leader will wait for