[jira] [Work started] (KAFKA-3443) Support regex topics in addSource() and stream()

[ https://issues.apache.org/jira/browse/KAFKA-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3443 started by Bill Bejeck. -- > Support regex topics in addSource() and stream() >

Re: [VOTE] KIP-45: Standardize KafkaConsumer API to use Collection

Ismael, Do we need to add old assign and subscribe that accepts List. It will get implicitly cast to collection with the new methods. The only problem comes from the methods that accepts varargs. -Harsha On Sat, May 7, 2016, at 05:53 PM, Mark Grover wrote: > Thanks Ismael, I agree w

Re: [VOTE] KIP-45: Standardize KafkaConsumer API to use Collection

Thanks Ismael, I agree with you, it makes sense to leave things the way they are in Kafka 0.10. On Fri, May 6, 2016 at 5:27 PM, Ismael Juma wrote: > Hi Mark, > > Thanks for the email. First of all, I'd like to mention that the `Unstable` > annotation has been removed from the new Java consumer i

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275431#comment-15275431 ] Jiangjie Qin commented on KAFKA-3565: - [~junrao] I think I figured out the reason why

[GitHub] kafka pull request: MINOR: Cleanup Admin Package

GitHub user Ishiihara opened a pull request: https://github.com/apache/kafka/pull/1342 MINOR: Cleanup Admin Package You can merge this pull request into a Git repository by running: $ git pull https://github.com/Ishiihara/kafka clean-admin-package Alternatively you can review

Re: KAFKA-3112

Thanks Ismael and Tao. Appreciate it. Sent from my iPhone > On May 7, 2016, at 1:14 AM, Ismael Juma wrote: > > Hi Raj and Tao, > > I just merged the KAFKA-3112 PR, so this issue will be fixed in 0.10.0.0. > > Thanks, > Ismael > >> On Fri, May 6, 2016 at 7:47 PM, tao xiao wrote: >> >> KAFKA-2657

[jira] [Work started] (KAFKA-3675) Add lz4 to parametrized `test_upgrade` system test

[ https://issues.apache.org/jira/browse/KAFKA-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3675 started by Ismael Juma. -- > Add lz4 to parametrized `test_upgrade` system test > --

[jira] [Created] (KAFKA-3675) Add lz4 to parametrized `test_upgrade` system test

Ismael Juma created KAFKA-3675: -- Summary: Add lz4 to parametrized `test_upgrade` system test Key: KAFKA-3675 URL: https://issues.apache.org/jira/browse/KAFKA-3675 Project: Kafka Issue Type: Test

Build failed in Jenkins: kafka-0.10.0-jdk7 #63

See Changes: [ismael] KAFKA-3160; Fix LZ4 Framing -- [...truncated 1675 lines...] kafka.server.EdgeCaseRequestTest > testMalformedHeaderRequest PASSED kafka.server.EdgeCaseRequestTest > testPro

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

See Changes: [ismael] KAFKA-3160; Fix LZ4 Framing -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-5 (docker Ubuntu ubuntu5 ubuntu yahoo-n

[jira] [Updated] (KAFKA-3160) Kafka LZ4 framing code miscalculates header checksum

[ https://issues.apache.org/jira/browse/KAFKA-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3160: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 1212

[jira] [Commented] (KAFKA-3160) Kafka LZ4 framing code miscalculates header checksum

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

[GitHub] kafka pull request: KAFKA-3160: Fix LZ4 Framing

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1212 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-3585) Shutdown slow when there is only one broker which is controller

[ https://issues.apache.org/jira/browse/KAFKA-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275312#comment-15275312 ] Taiyuan Zhang commented on KAFKA-3585: -- By the way, I just noticed that I was using 0

[jira] [Commented] (KAFKA-3674) Connector target state changes not propagated to all workers

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

[GitHub] kafka pull request: KAFKA-3674: Ensure connector target state chan...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1341 KAFKA-3674: Ensure connector target state changes propagated to worker You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-3

[GitHub] kafka pull request: HOTFIX: Ensure connector target state changes ...

Github user hachikuji closed the pull request at: https://github.com/apache/kafka/pull/1339 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is e

[jira] [Created] (KAFKA-3674) Connector target state changes not propagated to all workers

Jason Gustafson created KAFKA-3674: -- Summary: Connector target state changes not propagated to all workers Key: KAFKA-3674 URL: https://issues.apache.org/jira/browse/KAFKA-3674 Project: Kafka

Re: [VOTE] KIP-57: Interoperable LZ4 Framing

Vote Passed! I will update the wiki. -Dana On May 7, 2016 3:48 AM, "Ismael Juma" wrote: > Dana, a long time has passed since the vote started and there are enough > binding votes, so maybe it's time to declare that the vote has passed? > Please mark the KIP as adopted in the KIP page and move it

Re: How to submit a KIP?

Jayesh, I have given you the required permissions. The process is outlined in the following page (under the Process section): https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals In short, you should start a Discuss thread in the mailing list once the KIP is created. Tha

[jira] [Commented] (KAFKA-1981) Make log compaction point configurable

[ https://issues.apache.org/jira/browse/KAFKA-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275276#comment-15275276 ] Ismael Juma commented on KAFKA-1981: Sorry, my bad, you should have the required permi

Re: How to submit a KIP?

Thank you Ismael.My Apache id is jthakrar. Also, if you can let me know what the next step would be after creating the KIP. Thanks,Jayesh From: Ismael Juma To: dev@kafka.apache.org; Jayesh Thakrar Sent: Saturday, May 7, 2016 2:57 AM Subject: Re: How to submit a KIP? Hi Jayesh, You

Re: [VOTE] KIP-57: Interoperable LZ4 Framing

Dana, a long time has passed since the vote started and there are enough binding votes, so maybe it's time to declare that the vote has passed? Please mark the KIP as adopted in the KIP page and move it to the adopted table in the KIPs page once you do that. Ismael On 6 May 2016 22:16, "Ismael Jum

[jira] [Commented] (KAFKA-3385) Need to log "Rejected connection" as WARNING message

[ https://issues.apache.org/jira/browse/KAFKA-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275187#comment-15275187 ] Andrea Cosentino commented on KAFKA-3385: - Thanks [~ijuma] :-) > Need to log "Rej

[jira] [Commented] (KAFKA-3385) Need to log "Rejected connection" as WARNING message

[ https://issues.apache.org/jira/browse/KAFKA-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275186#comment-15275186 ] Ismael Juma commented on KAFKA-3385: I think the question here is whether we think tha

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

See

[jira] [Commented] (KAFKA-3385) Need to log "Rejected connection" as WARNING message

[ https://issues.apache.org/jira/browse/KAFKA-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275175#comment-15275175 ] Andrea Cosentino commented on KAFKA-3385: - Is there any news on this PR? It is ope

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

See

Build failed in Jenkins: kafka-0.10.0-jdk7 #62

See Changes: [ismael] KAFKA-3112; Warn instead of error on unresolvable bootstrap server -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H10 (do

Re: KAFKA-3112

Hi Raj and Tao, I just merged the KAFKA-3112 PR, so this issue will be fixed in 0.10.0.0. Thanks, Ismael On Fri, May 6, 2016 at 7:47 PM, tao xiao wrote: > KAFKA-2657 is unresolved so you can safely assume it hasn't been fixed yet. > > On Fri, 6 May 2016 at 07:38 Raj Tanneru wrote: > > > Yeah

[jira] [Resolved] (KAFKA-2657) Kafka clients fail to start if one of broker isn't resolved by DNS

[ https://issues.apache.org/jira/browse/KAFKA-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2657. Resolution: Duplicate This was fixed via KAFKA-3112. > Kafka clients fail to start if one of broker

[jira] [Resolved] (KAFKA-3112) One incorrect bootstrap server will prevent Kafka producer from opening

[ https://issues.apache.org/jira/browse/KAFKA-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3112. Resolution: Fixed Reviewer: Ismael Juma Fix Version/s: 0.10.0.0 > One incorrect boot

[jira] [Reopened] (KAFKA-3112) One incorrect bootstrap server will prevent Kafka producer from opening

[ https://issues.apache.org/jira/browse/KAFKA-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-3112: > One incorrect bootstrap server will prevent Kafka producer from opening >

[jira] [Updated] (KAFKA-3112) One incorrect bootstrap server will prevent Kafka producer from opening

[ https://issues.apache.org/jira/browse/KAFKA-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3112: --- Assignee: Jonathan Bond > One incorrect bootstrap server will prevent Kafka producer from opening > --

[jira] [Commented] (KAFKA-3112) One incorrect bootstrap server will prevent Kafka producer from opening

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

[GitHub] kafka pull request: KAFKA-3112: Change verification of bootstrap s...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/792 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

Re: How to submit a KIP?

Hi Jayesh, You need to create an Apache wiki account (if you haven't already) and then share your wiki id so that one of us can give you the required permissions. Thanks, Ismael On Sat, May 7, 2016 at 3:44 AM, Jayesh Thakrar wrote: > Hi, > I have created a Jira Issue - > https://issues.apache.