Jenkins build is back to normal : kafka-trunk-jdk8 #2402

See

Build failed in Jenkins: kafka-trunk-jdk9 #384

See Changes: [jason] KAFKA-6501; Dynamic broker config tests updates and metrics fix (#4539) -- [...truncated 1.47 MB...] kafka.controller.ReplicaStateMachineTest >

Re: [VOTE] KIP-251: Allow timestamp manipulation in Processor API

+1 Original message From: "Matthias J. Sax" Date: 2/8/18 6:05 PM (GMT-08:00) To: dev@kafka.apache.org Subject: [VOTE] KIP-251: Allow timestamp manipulation in Processor API Hi, I want to start the vote for KIP-251:

[VOTE] KIP-251: Allow timestamp manipulation in Processor API

Hi, I want to start the vote for KIP-251: https://cwiki.apache.org/confluence/display/KAFKA/KIP-251%3A+Allow+timestamp+manipulation+in+Processor+API -Matthias signature.asc Description: OpenPGP digital signature

Jenkins build is back to normal : kafka-trunk-jdk7 #3170

See

Re: [DISCUSS] KIP-251: Allow timestamp manipulation in Processor API

I updated the KIP to not include forwarding via child-index with the new `To` class. I also updated the PR accordingly. It seems there are not further comments atm. I am going to start a VOTE thread. Of course, you can always follow up on this thread. -Matthias On 2/7/18 2:10 PM, Guozhang

[jira] [Resolved] (KAFKA-6501) Add test to verify markPartitionsForTruncation after fetcher thread pool resize

[ https://issues.apache.org/jira/browse/KAFKA-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6501. Resolution: Fixed Fix Version/s: (was: 1.2.0) 1.1.0 > Add

Build failed in Jenkins: kafka-trunk-jdk7 #3169

See Changes: [github] MINOR: Add missing generics and surpress warning annotations (#4518) [github] KAFKA-3625: add docs for Kafka Streams test-utils (follow up) (#4493)

Build failed in Jenkins: kafka-trunk-jdk8 #2401

See Changes: [github] MINOR: improve security docs for Kafka Streams (#4532) [github] MINOR: Add missing generics and surpress warning annotations (#4518) [github] KAFKA-3625: add docs for Kafka Streams

[jira] [Created] (KAFKA-6548) Migrate committed offsets from ZooKeeper to Kafka

Manikandan P created KAFKA-6548: --- Summary: Migrate committed offsets from ZooKeeper to Kafka Key: KAFKA-6548 URL: https://issues.apache.org/jira/browse/KAFKA-6548 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-6547) group offset reset and begin_offset ignored/no effect

Dan created KAFKA-6547: -- Summary: group offset reset and begin_offset ignored/no effect Key: KAFKA-6547 URL: https://issues.apache.org/jira/browse/KAFKA-6547 Project: Kafka Issue Type: Bug

Build failed in Jenkins: kafka-trunk-jdk9 #383

See Changes: [github] MINOR: improve security docs for Kafka Streams (#4532) [github] MINOR: Add missing generics and surpress warning annotations (#4518) [github] KAFKA-3625: add docs for Kafka Streams

[jira] [Created] (KAFKA-6546) Add ENDPOINT_NOT_FOUND_ON_LEADER error code for missing listener

Rajini Sivaram created KAFKA-6546: - Summary: Add ENDPOINT_NOT_FOUND_ON_LEADER error code for missing listener Key: KAFKA-6546 URL: https://issues.apache.org/jira/browse/KAFKA-6546 Project: Kafka

Build failed in Jenkins: kafka-trunk-jdk8 #2400

See Changes: [github] MINOR: Update jetty, jackson, gradle and jacoco (#4547) [github] HOTFIX: Fix broken javadoc links on web docs(#4543) [jason] KAFKA-6362; Async auto-commit should discover coordinator if

[jira] [Resolved] (KAFKA-6545) AdminUtils.fetchTopicMetadataFromZk is not available in 1.0.0

[ https://issues.apache.org/jira/browse/KAFKA-6545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chong Wang resolved KAFKA-6545. --- Resolution: Not A Problem > AdminUtils.fetchTopicMetadataFromZk is not available in 1.0.0 >

[jira] [Created] (KAFKA-6545) AdminUtils.fetchTopicMetadataFromZk is not available in 1.0.0

Chong Wang created KAFKA-6545: - Summary: AdminUtils.fetchTopicMetadataFromZk is not available in 1.0.0 Key: KAFKA-6545 URL: https://issues.apache.org/jira/browse/KAFKA-6545 Project: Kafka Issue

Jenkins build is back to normal : kafka-1.1-jdk7 #23

See

[jira] [Resolved] (KAFKA-6345) NetworkClient.inFlightRequestCount() is not thread safe, causing ConcurrentModificationExceptions when sensors are read

[ https://issues.apache.org/jira/browse/KAFKA-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] radai rosenblatt resolved KAFKA-6345. - Resolution: Fixed > NetworkClient.inFlightRequestCount() is not thread safe, causing >

Re: Ability to raise a KIP

Andy, Thanks for your interest in doing a KIP. Just sign up at the AK wiki and provide your ID so we can grant you write access to create a new page in the wiki. However, I am not sure if I understand what you want to suggest? The key of a message cannot really change? Kafka topics store

[jira] [Created] (KAFKA-6544) kafka process should exit when it encounters "java.io.IOException: Too many open files"

Yu Yang created KAFKA-6544: -- Summary: kafka process should exit when it encounters "java.io.IOException: Too many open files" Key: KAFKA-6544 URL: https://issues.apache.org/jira/browse/KAFKA-6544 Project:

[jira] [Resolved] (KAFKA-6362) auto commit not work since coordinatorUnknown() is always true.

[ https://issues.apache.org/jira/browse/KAFKA-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6362. Resolution: Fixed Fix Version/s: 1.1.0 > auto commit not work since

[jira] [Resolved] (KAFKA-6543) Allow KTables to be bootstrapped at start up, like GKTables

[ https://issues.apache.org/jira/browse/KAFKA-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6543. Resolution: Duplicate > Allow KTables to be bootstrapped at start up, like GKTables >

Re: Eclipse or Intellij workspace setup

These articles may be useful: - https://developer.ibm.com/opentech/2016/06/06/how-to-develop-for-apache-kafka-using-eclipse/ - https://developer.ibm.com/opentech/2017/11/02/how-to-develop-for-apache-kafka-using-intellij-idea/ I personally prefer IntelliJ. Hope that helps. --Vahid From:

[jira] [Resolved] (KAFKA-6504) Connect: Some per-task-metrics not working

[ https://issues.apache.org/jira/browse/KAFKA-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6504. Resolution: Fixed Fix Version/s: 1.1.0 > Connect: Some per-task-metrics not working

Build failed in Jenkins: kafka-trunk-jdk8 #2399

See -- [...truncated 3.49 MB...] kafka.zookeeper.ZooKeeperClientTest > testPipelinedGetData PASSED kafka.zookeeper.ZooKeeperClientTest > testZNodeChildChangeHandlerForChildChange

[jira] [Created] (KAFKA-6543) Allow KTables to be bootstrapped at start up, like GKTables

Antony Stubbs created KAFKA-6543: Summary: Allow KTables to be bootstrapped at start up, like GKTables Key: KAFKA-6543 URL: https://issues.apache.org/jira/browse/KAFKA-6543 Project: Kafka

[jira] [Created] (KAFKA-6542) Tables should trigger joins too, not just streams

Antony Stubbs created KAFKA-6542: Summary: Tables should trigger joins too, not just streams Key: KAFKA-6542 URL: https://issues.apache.org/jira/browse/KAFKA-6542 Project: Kafka Issue Type:

why kafka index file use memory mapped files ,however log file doesn't?

Hi Experts, We know that kafka use memory mapped files for it's index files ,however it's log files don't use the memory mapped files technology. May I know why index files use memory mapped files, however log files don't use the same technology? Jacky

Jenkins build is back to normal : kafka-trunk-jdk9 #380

See