[jira] [Commented] (KAFKA-5575) SchemaBuilder should have a method to clone an existing Schema.

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

[jira] [Updated] (KAFKA-5560) LogManager should be able to create new logs based on free disk space

[ https://issues.apache.org/jira/browse/KAFKA-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx updated KAFKA-5560: -- Labels: kips (was: ) > LogManager should be able to create new logs based on free disk space >

[jira] [Created] (KAFKA-5576) Support Power platform by updating rocksdb

Yussuf Shaikh created KAFKA-5576: Summary: Support Power platform by updating rocksdb Key: KAFKA-5576 URL: https://issues.apache.org/jira/browse/KAFKA-5576 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-5576) Support Power platform by updating rocksdb

[ https://issues.apache.org/jira/browse/KAFKA-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080092#comment-16080092 ] Yussuf Shaikh commented on KAFKA-5576: -- RocksDB team have applied the fixes for Power

[jira] [Comment Edited] (KAFKA-5576) Support Power platform by updating rocksdb

[ https://issues.apache.org/jira/browse/KAFKA-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080092#comment-16080092 ] Yussuf Shaikh edited comment on KAFKA-5576 at 7/10/17 10:08 AM:

[jira] [Updated] (KAFKA-5576) Support Power platform by updating rocksdb

[ https://issues.apache.org/jira/browse/KAFKA-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yussuf Shaikh updated KAFKA-5576: - Attachment: KAFKA-5576.patch > Support Power platform by updating rocksdb > --

[jira] [Comment Edited] (KAFKA-5576) Support Power platform by updating rocksdb

[ https://issues.apache.org/jira/browse/KAFKA-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080092#comment-16080092 ] Yussuf Shaikh edited comment on KAFKA-5576 at 7/10/17 10:07 AM:

[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=16080123#comment-16080123 ] Viktor Somogyi commented on KAFKA-1044: --- [~ewencp] could you please look at my chang

[jira] [Commented] (KAFKA-5561) Rewrite TopicCommand using the new Admin client

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

[jira] [Commented] (KAFKA-5536) Tools splitted between Java and Scala implementation

[ https://issues.apache.org/jira/browse/KAFKA-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080163#comment-16080163 ] Paolo Patierno commented on KAFKA-5536: --- Hi [~ijuma], I have opened a PR on https:

[jira] [Commented] (KAFKA-4107) Support offset reset capability in Kafka Connect

[ https://issues.apache.org/jira/browse/KAFKA-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080346#comment-16080346 ] Sönke Liebau commented on KAFKA-4107: - Sounds good to me. I'll investigate the issue a

[jira] [Commented] (KAFKA-3268) Refactor existing CLI scripts to use new AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080358#comment-16080358 ] Viktor Somogyi commented on KAFKA-3268: --- [~granthenke] do you mind if I pick this up

[jira] [Commented] (KAFKA-3268) Refactor existing CLI scripts to use new AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080385#comment-16080385 ] Grant Henke commented on KAFKA-3268: Not at all. Feel free. > Refactor existing CLI s

[jira] [Assigned] (KAFKA-3268) Refactor existing CLI scripts to use new AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi reassigned KAFKA-3268: - Assignee: Viktor Somogyi > Refactor existing CLI scripts to use new AdminClient > ---

[jira] [Resolved] (KAFKA-5577) WindowedStreamPartitioner does not provide topic name to serializer

[ https://issues.apache.org/jira/browse/KAFKA-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-5577. Resolution: Fixed Fixed via https://github.com/apache/kafka/pull/2776 > WindowedStreamParti

[jira] [Commented] (KAFKA-5536) Tools splitted between Java and Scala implementation

[ https://issues.apache.org/jira/browse/KAFKA-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080562#comment-16080562 ] Ismael Juma commented on KAFKA-5536: Thanks for the PR. Answers to the questions: 1.

[jira] [Created] (KAFKA-5577) WindowedStreamPartitioner does not provide topic name to serializer

Matthias J. Sax created KAFKA-5577: -- Summary: WindowedStreamPartitioner does not provide topic name to serializer Key: KAFKA-5577 URL: https://issues.apache.org/jira/browse/KAFKA-5577 Project: Kafka

[jira] [Commented] (KAFKA-5562) Do streams state directory cleanup on a single thread

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

[jira] [Commented] (KAFKA-5536) Tools splitted between Java and Scala implementation

[ https://issues.apache.org/jira/browse/KAFKA-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080704#comment-16080704 ] Paolo Patierno commented on KAFKA-5536: --- Thanks Ismael ! 1. Good. I can recover the

[jira] [Created] (KAFKA-5578) Streams Task Assignor should consider the staleness of state directories when allocating tasks

Damian Guy created KAFKA-5578: - Summary: Streams Task Assignor should consider the staleness of state directories when allocating tasks Key: KAFKA-5578 URL: https://issues.apache.org/jira/browse/KAFKA-5578

[jira] [Commented] (KAFKA-5578) Streams Task Assignor should consider the staleness of state directories when allocating tasks

[ https://issues.apache.org/jira/browse/KAFKA-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080805#comment-16080805 ] Guozhang Wang commented on KAFKA-5578: -- Hey [~damianguy] do you mean that there could

[jira] [Resolved] (KAFKA-5157) Options for handling corrupt data during deserialization

[ https://issues.apache.org/jira/browse/KAFKA-5157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-5157. --- Resolution: Fixed Issue resolved by pull request 3423 [https://github.com/apache/kafka/pull/3423] > O

[jira] [Comment Edited] (KAFKA-4931) stop script fails due 4096 ps output limit

[ https://issues.apache.org/jira/browse/KAFKA-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080885#comment-16080885 ] Vahid Hashemian edited comment on KAFKA-4931 at 7/10/17 7:01 PM: ---

[jira] [Commented] (KAFKA-4931) stop script fails due 4096 ps output limit

[ https://issues.apache.org/jira/browse/KAFKA-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080885#comment-16080885 ] Vahid Hashemian commented on KAFKA-4931: [~tombentley] What exactly has the 4096 c

[jira] [Commented] (KAFKA-5157) Options for handling corrupt data during deserialization

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

[jira] [Updated] (KAFKA-5461) KIP-168: Add GlobalTopicCount metric per cluster

[ https://issues.apache.org/jira/browse/KAFKA-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Mendhekar updated KAFKA-5461: -- Summary: KIP-168: Add GlobalTopicCount metric per cluster (was: KIP-168: Add TotalTopic

[jira] [Commented] (KAFKA-5571) Possible deadlock during shutdown in setState in kafka streams 10.2

[ https://issues.apache.org/jira/browse/KAFKA-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081169#comment-16081169 ] Damian Guy commented on KAFKA-5571: --- It looks like it is because {{KafkaStreams#close}}

[jira] [Commented] (KAFKA-5579) SchemaBuilder.type(Schema.Type) should not allow null.

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

[jira] [Created] (KAFKA-5579) SchemaBuilder.type(Schema.Type) should not allow null.

Jeremy Custenborder created KAFKA-5579: -- Summary: SchemaBuilder.type(Schema.Type) should not allow null. Key: KAFKA-5579 URL: https://issues.apache.org/jira/browse/KAFKA-5579 Project: Kafka

[jira] [Commented] (KAFKA-5566) Instable test QueryableStateIntegrationTest.shouldAllowToQueryAfterThreadDied

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

[jira] [Comment Edited] (KAFKA-5571) Possible deadlock during shutdown in setState in kafka streams 10.2

[ https://issues.apache.org/jira/browse/KAFKA-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081255#comment-16081255 ] Guozhang Wang edited comment on KAFKA-5571 at 7/10/17 10:11 PM:

[jira] [Commented] (KAFKA-5571) Possible deadlock during shutdown in setState in kafka streams 10.2

[ https://issues.apache.org/jira/browse/KAFKA-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081255#comment-16081255 ] Guozhang Wang commented on KAFKA-5571: -- Is this already fixed in 0.11.0? [~enotheresk

[jira] [Created] (KAFKA-5580) Group rebalance delay only used with generation 0

Jason Gustafson created KAFKA-5580: -- Summary: Group rebalance delay only used with generation 0 Key: KAFKA-5580 URL: https://issues.apache.org/jira/browse/KAFKA-5580 Project: Kafka Issue Typ

[jira] [Created] (KAFKA-5581) Streams can be smarter in deciding when to create changelog topics for state stores

Guozhang Wang created KAFKA-5581: Summary: Streams can be smarter in deciding when to create changelog topics for state stores Key: KAFKA-5581 URL: https://issues.apache.org/jira/browse/KAFKA-5581 Pro

[jira] [Updated] (KAFKA-5545) Kafka Stream not able to successfully restart over new broker ip

[ https://issues.apache.org/jira/browse/KAFKA-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5545: - Affects Version/s: 0.10.2.1 > Kafka Stream not able to successfully restart over new broker ip > -

[jira] [Commented] (KAFKA-5576) Support Power platform by updating rocksdb

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

[jira] [Commented] (KAFKA-5545) Kafka Stream not able to successfully restart over new broker ip

[ https://issues.apache.org/jira/browse/KAFKA-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081698#comment-16081698 ] Guozhang Wang commented on KAFKA-5545: -- Thanks for the update. So when you mentioned