[jira] [Commented] (KAFKA-6262) Consumer should not use metadata that is older than the existing metadata

[ https://issues.apache.org/jira/browse/KAFKA-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263923#comment-16263923 ] Dong Lin commented on KAFKA-6262: - [~ijuma] Thanks much for the prompt reply! This makes s

[jira] [Commented] (KAFKA-5631) Use Jackson for serialising to JSON

[ https://issues.apache.org/jira/browse/KAFKA-5631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263894#comment-16263894 ] ASF GitHub Bot commented on KAFKA-5631: --- GitHub user umesh9794 opened a pull request

[jira] [Commented] (KAFKA-4499) Add "getAllKeys" API for querying windowed KTable stores

[ https://issues.apache.org/jira/browse/KAFKA-4499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263795#comment-16263795 ] ASF GitHub Bot commented on KAFKA-4499: --- GitHub user ConcurrencyPractitioner opened

[jira] [Created] (KAFKA-6265) GlobalKTable missing #queryableStoreName()

Antony Stubbs created KAFKA-6265: Summary: GlobalKTable missing #queryableStoreName() Key: KAFKA-6265 URL: https://issues.apache.org/jira/browse/KAFKA-6265 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-6174) Add methods in Options classes to keep binary compatibility with 0.11

[ https://issues.apache.org/jira/browse/KAFKA-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263646#comment-16263646 ] ASF GitHub Bot commented on KAFKA-6174: --- GitHub user lindong28 opened a pull request

[jira] [Updated] (KAFKA-6174) Add methods in Options classes to keep binary compatibility with 0.11

[ https://issues.apache.org/jira/browse/KAFKA-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6174: Summary: Add methods in Options classes to keep binary compatibility with 0.11 (was: Add methods in Options

[jira] [Commented] (KAFKA-6262) Consumer should not use metadata that is older than the existing metadata

[ https://issues.apache.org/jira/browse/KAFKA-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263631#comment-16263631 ] Ismael Juma commented on KAFKA-6262: I think we should do the "long term" fix and vers

[jira] [Commented] (KAFKA-5413) Log cleaner fails due to large offset in segment file

[ https://issues.apache.org/jira/browse/KAFKA-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263626#comment-16263626 ] Ismael Juma commented on KAFKA-5413: 0.10.2.2 hasn't been released and there are no im

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

Jiangjie Qin created KAFKA-6264: --- Summary: Log cleaner thread may die on legacy segment containing messages whose offsets are too large Key: KAFKA-6264 URL: https://issues.apache.org/jira/browse/KAFKA-6264

[jira] [Created] (KAFKA-6263) Expose metric for group metadata loading duration

Jason Gustafson created KAFKA-6263: -- Summary: Expose metric for group metadata loading duration Key: KAFKA-6263 URL: https://issues.apache.org/jira/browse/KAFKA-6263 Project: Kafka Issue Typ

[jira] [Commented] (KAFKA-6260) KafkaStream 1.0.0 does not starts correctly with Broker 0.11.0.1

[ https://issues.apache.org/jira/browse/KAFKA-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263585#comment-16263585 ] Matthias J. Sax commented on KAFKA-6260: I did a quick test locally but could not

[jira] [Commented] (KAFKA-6259) Make KafkaStreams.cleanup() clean global state directory

[ https://issues.apache.org/jira/browse/KAFKA-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263514#comment-16263514 ] ASF GitHub Bot commented on KAFKA-6259: --- GitHub user mjsax opened a pull request:

[jira] [Assigned] (KAFKA-6259) Make KafkaStreams.cleanup() clean global state directory

[ https://issues.apache.org/jira/browse/KAFKA-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-6259: -- Assignee: Matthias J. Sax > Make KafkaStreams.cleanup() clean global state directory >

[jira] [Commented] (KAFKA-6074) Use ZookeeperClient in ReplicaManager and Partition

[ https://issues.apache.org/jira/browse/KAFKA-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263468#comment-16263468 ] ASF GitHub Bot commented on KAFKA-6074: --- GitHub user tedyu opened a pull request:

[jira] [Commented] (KAFKA-6074) Use ZookeeperClient in ReplicaManager and Partition

[ https://issues.apache.org/jira/browse/KAFKA-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263463#comment-16263463 ] ASF GitHub Bot commented on KAFKA-6074: --- Github user tedyu closed the pull request a

[jira] [Commented] (KAFKA-6249) Interactive query downtime when node goes down even with standby replicas

[ https://issues.apache.org/jira/browse/KAFKA-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263424#comment-16263424 ] Matthias J. Sax commented on KAFKA-6249: Atm, it is not possible to query StandbyT

[jira] [Commented] (KAFKA-6262) Consumer should not uses metadata that is older than the existing metadata

[ https://issues.apache.org/jira/browse/KAFKA-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263374#comment-16263374 ] Dong Lin commented on KAFKA-6262: - [~junrao] [~ijuma] Can you comment on the solution of t

[jira] [Updated] (KAFKA-6262) Consumer should not use metadata that is older than the existing metadata

[ https://issues.apache.org/jira/browse/KAFKA-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6262: Summary: Consumer should not use metadata that is older than the existing metadata (was: Consumer should no

[jira] [Updated] (KAFKA-6262) Consumer should not use metadata that is older than the existing metadata

[ https://issues.apache.org/jira/browse/KAFKA-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6262: Issue Type: Bug (was: Improvement) > Consumer should not use metadata that is older than the existing metad

[jira] [Created] (KAFKA-6262) Consumer should not uses metadata that is older than the existing metadata

Dong Lin created KAFKA-6262: --- Summary: Consumer should not uses metadata that is older than the existing metadata Key: KAFKA-6262 URL: https://issues.apache.org/jira/browse/KAFKA-6262 Project: Kafka

[jira] [Commented] (KAFKA-5646) Use async ZookeeperClient for DynamicConfigManager

[ https://issues.apache.org/jira/browse/KAFKA-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263370#comment-16263370 ] ASF GitHub Bot commented on KAFKA-5646: --- Github user asfgit closed the pull request

[jira] [Updated] (KAFKA-6249) Interactive query downtime when node goes down even with standby replicas

[ https://issues.apache.org/jira/browse/KAFKA-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles Crain updated KAFKA-6249: - Description: In a multi-node Kafka Streams application that uses interactive queries, the queryab

[jira] [Updated] (KAFKA-6249) Interactive query downtime when node goes down even with standby replicas

[ https://issues.apache.org/jira/browse/KAFKA-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles Crain updated KAFKA-6249: - Description: In a multi-node Kafka Streams application that uses interactive queries, the queryab

[jira] [Commented] (KAFKA-6249) Interactive query downtime when node goes down even with standby replicas

[ https://issues.apache.org/jira/browse/KAFKA-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263231#comment-16263231 ] Charles Crain commented on KAFKA-6249: -- KAFKA-6144 is definitely related. Solving it

[jira] [Updated] (KAFKA-6260) KafkaStream 1.0.0 does not starts correctly with Broker 0.11.0.1

[ https://issues.apache.org/jira/browse/KAFKA-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seweryn Habdank-Wojewodzki updated KAFKA-6260: -- Description: The new KafkaStreams API (v. 1.0.0), which uses StreamsBuil

[jira] [Updated] (KAFKA-6260) KafkaStream 1.0.0 does not starts correctly with Broker 0.11.0.1

[ https://issues.apache.org/jira/browse/KAFKA-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seweryn Habdank-Wojewodzki updated KAFKA-6260: -- Summary: KafkaStream 1.0.0 does not starts correctly with Broker 0.11.0.1

[jira] [Updated] (KAFKA-6260) KafkaStream 1.0.0 does not strarts correctly with Broker 0.11.0.1

[ https://issues.apache.org/jira/browse/KAFKA-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seweryn Habdank-Wojewodzki updated KAFKA-6260: -- Description: The new KafkaStreams API, which uses StreamsBuilder class h

[jira] [Comment Edited] (KAFKA-6260) KafkaStream 1.0.0 does not strarts correctly with Broker 0.11.0.1

[ https://issues.apache.org/jira/browse/KAFKA-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262887#comment-16262887 ] Seweryn Habdank-Wojewodzki edited comment on KAFKA-6260 at 11/22/17 7:32 PM: ---

[jira] [Commented] (KAFKA-6253) Improve sink connector topic regex validation

[ https://issues.apache.org/jira/browse/KAFKA-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263058#comment-16263058 ] ASF GitHub Bot commented on KAFKA-6253: --- GitHub user jklukas opened a pull request:

[jira] [Assigned] (KAFKA-6253) Improve sink connector topic regex validation

[ https://issues.apache.org/jira/browse/KAFKA-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Klukas reassigned KAFKA-6253: -- Assignee: Jeff Klukas (was: Randall Hauch) > Improve sink connector topic regex validation > -

[jira] [Resolved] (KAFKA-4827) Kafka connect: error with special characters in connector name

[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-4827. -- Resolution: Fixed Fix Version/s: (was: 0.11.0.3)

[jira] [Commented] (KAFKA-4827) Kafka connect: error with special characters in connector name

[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263010#comment-16263010 ] ASF GitHub Bot commented on KAFKA-4827: --- Github user asfgit closed the pull request

[jira] [Commented] (KAFKA-6259) Make KafkaStreams.cleanup() clean global state directory

[ https://issues.apache.org/jira/browse/KAFKA-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262987#comment-16262987 ] Tommy Becker commented on KAFKA-6259: - I literally just noticed this yesterday, and wa

[jira] [Commented] (KAFKA-6260) KafkaStream 1.0.0 does not strarts correctly with Broker 0.11.0.1

[ https://issues.apache.org/jira/browse/KAFKA-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262904#comment-16262904 ] Rajini Sivaram commented on KAFKA-6260: --- [~ijuma] Typically we have a single thread

[jira] [Commented] (KAFKA-6260) KafkaStream 1.0.0 does not strarts correctly with Broker 0.11.0.1

[ https://issues.apache.org/jira/browse/KAFKA-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262887#comment-16262887 ] Seweryn Habdank-Wojewodzki commented on KAFKA-6260: --- @guozhang zwang: at

[jira] [Commented] (KAFKA-6260) KafkaStream 1.0.0 does not strarts correctly with Broker 0.11.0.1

[ https://issues.apache.org/jira/browse/KAFKA-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262869#comment-16262869 ] Ismael Juma commented on KAFKA-6260: [~rsivaram], the Selector NPE above looks odd. Se

[jira] [Commented] (KAFKA-6205) Have State Stores Restore Before Initializing Toplogy

[ https://issues.apache.org/jira/browse/KAFKA-6205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262865#comment-16262865 ] Rainer Guessner commented on KAFKA-6205: StateRestoreListener does not help as its

[jira] [Commented] (KAFKA-6261) Request logging throws exception if acks=0

[ https://issues.apache.org/jira/browse/KAFKA-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262852#comment-16262852 ] ASF GitHub Bot commented on KAFKA-6261: --- GitHub user ijuma opened a pull request:

[jira] [Commented] (KAFKA-6260) KafkaStream 1.0.0 does not strarts correctly with Broker 0.11.0.1

[ https://issues.apache.org/jira/browse/KAFKA-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262849#comment-16262849 ] Guozhang Wang commented on KAFKA-6260: -- Is this consistently producible at starting u

[jira] [Created] (KAFKA-6261) Request logging throws exception if acks=0

Ismael Juma created KAFKA-6261: -- Summary: Request logging throws exception if acks=0 Key: KAFKA-6261 URL: https://issues.apache.org/jira/browse/KAFKA-6261 Project: Kafka Issue Type: Bug Affe

[jira] [Created] (KAFKA-6260) KafkaStream 1.0.0 does not strarts correctly with Broker 0.11.0.1

Seweryn Habdank-Wojewodzki created KAFKA-6260: - Summary: KafkaStream 1.0.0 does not strarts correctly with Broker 0.11.0.1 Key: KAFKA-6260 URL: https://issues.apache.org/jira/browse/KAFKA-6260

[jira] [Resolved] (KAFKA-1044) change log4j to slf4j

[ https://issues.apache.org/jira/browse/KAFKA-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-1044. Resolution: Fixed Fix Version/s: 1.1.0 > change log4j to slf4j > -- > >

[jira] [Commented] (KAFKA-1044) change log4j to slf4j

[ https://issues.apache.org/jira/browse/KAFKA-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262766#comment-16262766 ] ASF GitHub Bot commented on KAFKA-1044: --- Github user asfgit closed the pull request

[jira] [Created] (KAFKA-6259) Make KafkaStreams.cleanup() clean global state directory

Damian Guy created KAFKA-6259: - Summary: Make KafkaStreams.cleanup() clean global state directory Key: KAFKA-6259 URL: https://issues.apache.org/jira/browse/KAFKA-6259 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-4930) Connect Rest API allows creating connectors with an empty name

[ https://issues.apache.org/jira/browse/KAFKA-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262465#comment-16262465 ] Sönke Liebau commented on KAFKA-4930: - @[~rhauch] - did you have a chance yet to have

[jira] [Resolved] (KAFKA-6251) Update kafka-configs.sh to use the new AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-6251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-6251. --- Resolution: Duplicate Fix Version/s: (was: 1.1.0) > Update kafka-configs.sh to use

[jira] [Comment Edited] (KAFKA-6251) Update kafka-configs.sh to use the new AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-6251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262428#comment-16262428 ] Rajini Sivaram edited comment on KAFKA-6251 at 11/22/17 12:24 PM: --

[jira] [Updated] (KAFKA-5722) Refactor ConfigCommand to use the AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-5722: -- Fix Version/s: 1.1.0 > Refactor ConfigCommand to use the AdminClient > -

[jira] [Commented] (KAFKA-6251) Update kafka-configs.sh to use the new AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-6251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262428#comment-16262428 ] Rajini Sivaram commented on KAFKA-6251: --- [~tombentley] Yes, that is the same one. cl

[jira] [Comment Edited] (KAFKA-6257) KafkaConsumer was hung when bootstrap servers was not existed

[ https://issues.apache.org/jira/browse/KAFKA-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262237#comment-16262237 ] Sönke Liebau edited comment on KAFKA-6257 at 11/22/17 10:20 AM:

[jira] [Commented] (KAFKA-6257) KafkaConsumer was hung when bootstrap servers was not existed

[ https://issues.apache.org/jira/browse/KAFKA-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262237#comment-16262237 ] Sönke Liebau commented on KAFKA-6257: - This is probably a duplicate of the existing ti

[jira] [Commented] (KAFKA-6251) Update kafka-configs.sh to use the new AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-6251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262192#comment-16262192 ] Tom Bentley commented on KAFKA-6251: You're right, but then https://issues.apache.org/

[jira] [Updated] (KAFKA-6258) SSLTransportLayer should keep reading from socket until either the buffer is full or the socket has no more data

[ https://issues.apache.org/jira/browse/KAFKA-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6258: Description: When consumer uses plaintext and there is remaining data in consumer's buffer, consumer.poll()

[jira] [Updated] (KAFKA-6258) SSLTransportLayer should keep reading from socket until either the buffer is full or the socket has no more data

[ https://issues.apache.org/jira/browse/KAFKA-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6258: Description: When consumer uses plaintext and there is remaining data in consumer's buffer, consumer.poll()

[jira] [Updated] (KAFKA-6258) SSLTransportLayer should keep reading from socket until either the buffer is full or the socket has no more data

[ https://issues.apache.org/jira/browse/KAFKA-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6258: Description: When consumer uses plaintext and there is remaining data in consumer's buffer, consumer.poll()

[jira] [Updated] (KAFKA-6258) SSLTransportLayer should keep reading from socket until either the buffer is full or the socket has no more data

[ https://issues.apache.org/jira/browse/KAFKA-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6258: Description: When consumer uses plaintext and there is remaining data in consumer's buffer, consumer.poll()