[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=16076915#comment-16076915 ] Randall Hauch commented on KAFKA-4107: -- This is definitely a good tool to have. There's a new

[jira] [Commented] (KAFKA-4490) Add Global Table support to Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076901#comment-16076901 ] Matthias J. Sax commented on KAFKA-4490: See: https://issues.apache.org/jira/browse/KAFKA-4628 >

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

Matthias J. Sax created KAFKA-5566: -- Summary: Instable test QueryableStateIntegrationTest.shouldAllowToQueryAfterThreadDied Key: KAFKA-5566 URL: https://issues.apache.org/jira/browse/KAFKA-5566

[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=16076052#comment-16076052 ] Sönke Liebau commented on KAFKA-4827: - There is a few more special characters that cause similar

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

huxihx created KAFKA-5560: - Summary: LogManager should be able to create new logs based on free disk space Key: KAFKA-5560 URL: https://issues.apache.org/jira/browse/KAFKA-5560 Project: Kafka Issue

[jira] [Commented] (KAFKA-5464) StreamsKafkaClient should not use StreamsConfig.POLL_MS_CONFIG

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

[jira] [Created] (KAFKA-5563) Clarify handling of connector name in config

Sönke Liebau created KAFKA-5563: --- Summary: Clarify handling of connector name in config Key: KAFKA-5563 URL: https://issues.apache.org/jira/browse/KAFKA-5563 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-3331) Refactor TopicCommand to make it testable and add unit tests

[ https://issues.apache.org/jira/browse/KAFKA-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076252#comment-16076252 ] Paolo Patierno commented on KAFKA-3331: --- [~gwenshap] I opened this JIRA

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

Damian Guy created KAFKA-5562: - Summary: Do streams state directory cleanup on a single thread Key: KAFKA-5562 URL: https://issues.apache.org/jira/browse/KAFKA-5562 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-5529) ConsoleProducer uses deprecated BaseProducer

[ https://issues.apache.org/jira/browse/KAFKA-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5529: --- Fix Version/s: 0.12.0.0 > ConsoleProducer uses deprecated BaseProducer >

[jira] [Commented] (KAFKA-4468) Correctly calculate the window end timestamp after read from state stores

[ https://issues.apache.org/jira/browse/KAFKA-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076373#comment-16076373 ] Evgeny Veretennikov commented on KAFKA-4468: Sorry, guys, I missed javadoc comment to

[jira] [Resolved] (KAFKA-5508) Documentation for altering topics

[ https://issues.apache.org/jira/browse/KAFKA-5508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-5508. --- Resolution: Fixed Fix Version/s: 0.11.0.1 0.11.1.0 Issue resolved by pull

[jira] [Updated] (KAFKA-5512) KafkaConsumer: High memory allocation rate when idle

[ https://issues.apache.org/jira/browse/KAFKA-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5512: --- Fix Version/s: 0.10.2.2 > KafkaConsumer: High memory allocation rate when idle >

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

Paolo Patierno created KAFKA-5561: - Summary: Rewrite TopicCommand using the new Admin client Key: KAFKA-5561 URL: https://issues.apache.org/jira/browse/KAFKA-5561 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-5508) Documentation for altering topics

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

[jira] [Commented] (KAFKA-3362) Update protocol schema and field doc strings

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

[jira] [Commented] (KAFKA-4468) Correctly calculate the window end timestamp after read from state stores

[ https://issues.apache.org/jira/browse/KAFKA-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076472#comment-16076472 ] Evgeny Veretennikov commented on KAFKA-4468: Let me show you such example: {code:java} final

[jira] [Commented] (KAFKA-5070) org.apache.kafka.streams.errors.LockException: task [0_18] Failed to lock the state directory: /opt/rocksdb/pulse10/0_18

[ https://issues.apache.org/jira/browse/KAFKA-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076489#comment-16076489 ] Damian Guy commented on KAFKA-5070: --- [~mjsax] https://issues.apache.org/jira/browse/KAFKA-5167 hasn't

[jira] [Comment Edited] (KAFKA-4468) Correctly calculate the window end timestamp after read from state stores

[ https://issues.apache.org/jira/browse/KAFKA-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076472#comment-16076472 ] Evgeny Veretennikov edited comment on KAFKA-4468 at 7/6/17 1:13 PM:

[jira] [Created] (KAFKA-5564) Fail to create topics with error 'While recording the replica LEO, the partition [topic2,0] hasn't been created'

Klearchos Chaloulos created KAFKA-5564: -- Summary: Fail to create topics with error 'While recording the replica LEO, the partition [topic2,0] hasn't been created' Key: KAFKA-5564 URL:

[jira] [Issue Comment Deleted] (KAFKA-5070) org.apache.kafka.streams.errors.LockException: task [0_18] Failed to lock the state directory: /opt/rocksdb/pulse10/0_18

[ https://issues.apache.org/jira/browse/KAFKA-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5070: -- Comment: was deleted (was: [~mjsax] https://issues.apache.org/jira/browse/KAFKA-5167 hasn't fixed the

[jira] [Commented] (KAFKA-4468) Correctly calculate the window end timestamp after read from state stores

[ https://issues.apache.org/jira/browse/KAFKA-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076830#comment-16076830 ] Matthias J. Sax commented on KAFKA-4468: Thanks for following up. About storing the window size --

[jira] [Commented] (KAFKA-5407) Mirrormaker dont start after upgrade

[ https://issues.apache.org/jira/browse/KAFKA-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16077505#comment-16077505 ] huxihx commented on KAFKA-5407: --- [~fvegaucr] Did you find any exceptions thrown when new consumer was used?

[jira] [Commented] (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:comment-tabpanel=16077506#comment-16077506 ] huxihx commented on KAFKA-5560: --- [~junrao] Do you see it as a reasonable requirement? > LogManager should

[jira] [Commented] (KAFKA-5467) setting offset retention minutes to a lower value is not reflecting

[ https://issues.apache.org/jira/browse/KAFKA-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16077536#comment-16077536 ] huxihx commented on KAFKA-5467: --- Log cleaner does not clean the active log segment. How many log segments do

[jira] [Resolved] (KAFKA-3745) Consider adding join key to ValueJoiner interface

[ https://issues.apache.org/jira/browse/KAFKA-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-3745. Resolution: Duplicate See

[jira] [Assigned] (KAFKA-4726) ValueMapper should have (read) access to key

[ https://issues.apache.org/jira/browse/KAFKA-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-4726: -- Assignee: Jeyhun Karimov > ValueMapper should have (read) access to key >

[jira] [Commented] (KAFKA-5318) Streams state may be misleading

[ https://issues.apache.org/jira/browse/KAFKA-5318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16077336#comment-16077336 ] Matthias J. Sax commented on KAFKA-5318: Is this contained by KAFKA-5372 ? \cc [~enothereska] >

[jira] [Updated] (KAFKA-4125) Provide low-level Processor API meta data in DSL layer

[ https://issues.apache.org/jira/browse/KAFKA-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4125: --- Labels: kip (was: ) > Provide low-level Processor API meta data in DSL layer >

[jira] [Updated] (KAFKA-4125) Provide low-level Processor API meta data in DSL layer

[ https://issues.apache.org/jira/browse/KAFKA-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4125: --- Description: For Processor API, user can get meta data like record offset, timestamp etc via

[jira] [Created] (KAFKA-5568) Transformations that mutate topic-partitions break sink connectors that manage their own configuration

Ewen Cheslack-Postava created KAFKA-5568: Summary: Transformations that mutate topic-partitions break sink connectors that manage their own configuration Key: KAFKA-5568 URL:

[jira] [Commented] (KAFKA-5407) Mirrormaker dont start after upgrade

[ https://issues.apache.org/jira/browse/KAFKA-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16077460#comment-16077460 ] Fernando Vega commented on KAFKA-5407: -- listed are the config files: Broker: {noformat} ### ### This

[jira] [Assigned] (KAFKA-5565) Add a broker metric specifying the number of consumer group rebalances in progress

[ https://issues.apache.org/jira/browse/KAFKA-5565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe reassigned KAFKA-5565: -- Assignee: Colin P. McCabe > Add a broker metric specifying the number of consumer

[jira] [Created] (KAFKA-5567) With transformations that mutate the topic-partition committing offsets should to refer to the original topic-partition

Konstantine Karantasis created KAFKA-5567: - Summary: With transformations that mutate the topic-partition committing offsets should to refer to the original topic-partition Key: KAFKA-5567 URL:

[jira] [Commented] (KAFKA-5407) Mirrormaker dont start after upgrade

[ https://issues.apache.org/jira/browse/KAFKA-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16077458#comment-16077458 ] Fernando Vega commented on KAFKA-5407: -- [~huxi_2b] So we manage to bring the mirrormakers up. However

[jira] [Commented] (KAFKA-5567) With transformations that mutate the topic-partition committing offsets should to refer to the original topic-partition

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