[jira] [Created] (KAFKA-7301) KTable to KTable join invocation does not resolve in Scala DSL

Michal created KAFKA-7301: - Summary: KTable to KTable join invocation does not resolve in Scala DSL Key: KAFKA-7301 URL: https://issues.apache.org/jira/browse/KAFKA-7301 Project: Kafka Issue Type: B

[jira] [Commented] (KAFKA-7282) Failed to read `log header` from file channel

[ https://issues.apache.org/jira/browse/KAFKA-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582084#comment-16582084 ] Alastair Munro commented on KAFKA-7282: --- We set these settings below for the kafka*

[jira] [Comment Edited] (KAFKA-7282) Failed to read `log header` from file channel

[ https://issues.apache.org/jira/browse/KAFKA-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582084#comment-16582084 ] Alastair Munro edited comment on KAFKA-7282 at 8/16/18 7:42 AM: ---

[jira] [Updated] (KAFKA-7301) KTable to KTable join invocation does not resolve in Scala DSL

[ https://issues.apache.org/jira/browse/KAFKA-7301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal updated KAFKA-7301: -- Description: I found a peculiar problem while doing KTable to KTable join using Scala DSL. The following code:

[jira] [Commented] (KAFKA-7119) Intermittent test failure with GSSAPI authentication failure

[ https://issues.apache.org/jira/browse/KAFKA-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582135#comment-16582135 ] ASF GitHub Bot commented on KAFKA-7119: --- rajinisivaram closed pull request #5509: K

[jira] [Resolved] (KAFKA-7119) Intermittent test failure with GSSAPI authentication failure

[ https://issues.apache.org/jira/browse/KAFKA-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-7119. --- Resolution: Fixed > Intermittent test failure with GSSAPI authentication failure > --

[jira] [Commented] (KAFKA-6690) Priorities for Source Topics

[ https://issues.apache.org/jira/browse/KAFKA-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582410#comment-16582410 ] Nick Afshartous commented on KAFKA-6690: [~guozhang] I called for a VOTE on the d

[jira] [Commented] (KAFKA-7291) kafka-console-consumer.sh waits on inexistent topic

[ https://issues.apache.org/jira/browse/KAFKA-7291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582420#comment-16582420 ] HUSLEAG Dumitru commented on KAFKA-7291: Yes that behavior works for me. But we

[jira] [Commented] (KAFKA-7277) Migrate Streams API to Duration instead of longMs times

[ https://issues.apache.org/jira/browse/KAFKA-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582662#comment-16582662 ] Nikolay Izhikov commented on KAFKA-7277: [~vvcephei] KIP-358 created. I've added

[jira] [Commented] (KAFKA-7301) KTable to KTable join invocation does not resolve in Scala DSL

[ https://issues.apache.org/jira/browse/KAFKA-7301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582742#comment-16582742 ] Guozhang Wang commented on KAFKA-7301: -- I think it is being fixed in this PR: https

[jira] [Commented] (KAFKA-7301) KTable to KTable join invocation does not resolve in Scala DSL

[ https://issues.apache.org/jira/browse/KAFKA-7301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582747#comment-16582747 ] Michal commented on KAFKA-7301: --- Awsome:) > KTable to KTable join invocation does not reso

[jira] [Updated] (KAFKA-7301) KTable to KTable join invocation does not resolve in Scala DSL

[ https://issues.apache.org/jira/browse/KAFKA-7301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-7301: --- Affects Version/s: 2.0.0 > KTable to KTable join invocation does not resolve in Scala DSL > -

[jira] [Updated] (KAFKA-7277) Migrate Streams API to Duration instead of longMs times

[ https://issues.apache.org/jira/browse/KAFKA-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-7277: --- Labels: beginner kip newbie (was: beginner needs-kip newbie) > Migrate Streams API to Durati

[jira] [Commented] (KAFKA-7298) Concurrent DeleteRecords can lead to fatal OutOfSequence error in producer

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

[jira] [Updated] (KAFKA-7277) Migrate Streams API to Duration instead of longMs times

[ https://issues.apache.org/jira/browse/KAFKA-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-7277: --- Description: Right now Streams API unversally represents time as ms-since-unix-epoch. There'

[jira] [Commented] (KAFKA-7296) Producer should handle COORDINATOR_LOADING error in TxnOffsetCommit

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

[jira] [Resolved] (KAFKA-7296) Producer should handle COORDINATOR_LOADING error in TxnOffsetCommit

[ https://issues.apache.org/jira/browse/KAFKA-7296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7296. Resolution: Fixed > Producer should handle COORDINATOR_LOADING error in TxnOffsetCommit > -

[jira] [Created] (KAFKA-7302) Remove Java7 examples from Streams Docs

Matthias J. Sax created KAFKA-7302: -- Summary: Remove Java7 examples from Streams Docs Key: KAFKA-7302 URL: https://issues.apache.org/jira/browse/KAFKA-7302 Project: Kafka Issue Type: Improve

[jira] [Commented] (KAFKA-7186) Controller uses too much memory when sending out UpdateMetadataRequest that can cause OutOfMemoryError

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

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582931#comment-16582931 ] Matthias J. Sax commented on KAFKA-7190: I want to through out another thought:

[jira] [Commented] (KAFKA-4748) Need a way to shutdown all workers in a Streams application at the same time

[ https://issues.apache.org/jira/browse/KAFKA-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16583062#comment-16583062 ] Wladimir Schmidt commented on KAFKA-4748: - I think, it would be very useful to ha

[jira] [Created] (KAFKA-7303) Kafka client is stuck when specifying wrong brokkers

Chun Zhang created KAFKA-7303: - Summary: Kafka client is stuck when specifying wrong brokkers Key: KAFKA-7303 URL: https://issues.apache.org/jira/browse/KAFKA-7303 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-7284) Producer getting fenced may cause Streams to shut down

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

[jira] [Updated] (KAFKA-7303) Kafka client is stuck when specifying wrong brokers

[ https://issues.apache.org/jira/browse/KAFKA-7303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chun Zhang updated KAFKA-7303: -- Summary: Kafka client is stuck when specifying wrong brokers (was: Kafka client is stuck when specifyi

[jira] [Commented] (KAFKA-7299) batch LeaderAndIsr requests during auto preferred leader election

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

[jira] [Resolved] (KAFKA-7299) batch LeaderAndIsr requests during auto preferred leader election

[ https://issues.apache.org/jira/browse/KAFKA-7299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-7299. Resolution: Fixed Fix Version/s: 2.1.0 Merged the PR to trunk. > batch LeaderAndIsr requests during

[jira] [Comment Edited] (KAFKA-6303) Potential lack of synchronization in NioEchoServer#AcceptorThread

[ https://issues.apache.org/jira/browse/KAFKA-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333251#comment-16333251 ] Ted Yu edited comment on KAFKA-6303 at 8/16/18 11:06 PM: - +1 from

[jira] [Commented] (KAFKA-7051) Improve the efficiency of the ReplicaManager when there are many partitions

[ https://issues.apache.org/jira/browse/KAFKA-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16583248#comment-16583248 ] Andy Bryant commented on KAFKA-7051: We've seen this codeblock taking considerable CP

[jira] [Comment Edited] (KAFKA-7051) Improve the efficiency of the ReplicaManager when there are many partitions

[ https://issues.apache.org/jira/browse/KAFKA-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16583248#comment-16583248 ] Andy Bryant edited comment on KAFKA-7051 at 8/17/18 1:23 AM: -