[jira] [Resolved] (KAFKA-2866) Bump up commons-collections version to 3.2.2 to address a security flaw

[ https://issues.apache.org/jira/browse/KAFKA-2866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2866. Resolution: Fixed Assignee: Ismael Juma (was: Grant Henke) Reviewer: Gwen Shapira Fixed

[jira] [Resolved] (KAFKA-3453) Transient test failures due to MiniKDC port allocation strategy

[ https://issues.apache.org/jira/browse/KAFKA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3453. Resolution: Fixed Fix Version/s: (was: 0.10.0.1) 0.10.0.0 Fixed as par

[jira] [Updated] (KAFKA-3453) Transient test failures due to MiniKDC port allocation strategy

[ https://issues.apache.org/jira/browse/KAFKA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3453: --- Reviewer: Gwen Shapira > Transient test failures due to MiniKDC port allocation strategy > ---

[jira] [Created] (KAFKA-3488) commitAsync() fails if metadata update creates new SASL/SSL connection

Rajini Sivaram created KAFKA-3488: - Summary: commitAsync() fails if metadata update creates new SASL/SSL connection Key: KAFKA-3488 URL: https://issues.apache.org/jira/browse/KAFKA-3488 Project: Kafka

[jira] [Commented] (KAFKA-3488) commitAsync() fails if metadata update creates new SASL/SSL connection

[ https://issues.apache.org/jira/browse/KAFKA-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219731#comment-15219731 ] Ismael Juma commented on KAFKA-3488: Good catch [~rsivaram]. Thoughts [~hachikuji]? >

[jira] [Updated] (KAFKA-3488) commitAsync() fails if metadata update creates new SASL/SSL connection

[ https://issues.apache.org/jira/browse/KAFKA-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3488: --- Fix Version/s: 0.10.0.0 > commitAsync() fails if metadata update creates new SASL/SSL connection > ---

Re: KIP-4 Wiki Update

Hi Grant, I had a second look at the proposed changes to Metadata Request and Response and it seems to me that having a `controller_id` field would be more efficient for non-trivial cases than having a `is_controller` field for each broker (which would be false for all but 1 case). Similar, but

[jira] [Commented] (KAFKA-3456) In-house KafkaMetric misreports metrics when periodically observed

[ https://issues.apache.org/jira/browse/KAFKA-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219894#comment-15219894 ] The Data Lorax commented on KAFKA-3456: --- OK, I'm getting the feeling there is little

[jira] [Assigned] (KAFKA-2910) Failure in kafka.api.SslEndToEndAuthorizationTest.testNoGroupAcl

[ https://issues.apache.org/jira/browse/KAFKA-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-2910: - Assignee: Rajini Sivaram > Failure in kafka.api.SslEndToEndAuthorizationTest.testNoGroupA

Re: KIP-4 Wiki Update

> > I had a second look at the proposed changes to Metadata Request and > Response and it seems to me that having a `controller_id` field would be > more efficient for non-trivial cases than having a `is_controller` field > for each broker (which would be false for all but 1 case). I agree this

[jira] [Commented] (KAFKA-2910) Failure in kafka.api.SslEndToEndAuthorizationTest.testNoGroupAcl

[ https://issues.apache.org/jira/browse/KAFKA-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219926#comment-15219926 ] Rajini Sivaram commented on KAFKA-2910: --- Came across this failure while running the

[jira] [Commented] (KAFKA-2910) Failure in kafka.api.SslEndToEndAuthorizationTest.testNoGroupAcl

[ https://issues.apache.org/jira/browse/KAFKA-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219956#comment-15219956 ] Ismael Juma commented on KAFKA-2910: Interesting, I think we have at least one other J

[jira] [Commented] (KAFKA-2910) Failure in kafka.api.SslEndToEndAuthorizationTest.testNoGroupAcl

[ https://issues.apache.org/jira/browse/KAFKA-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219967#comment-15219967 ] Rajini Sivaram commented on KAFKA-2910: --- [~ijuma] Yes, I will try out a fix, do some

[jira] [Updated] (KAFKA-2910) Failure in kafka.api.SslEndToEndAuthorizationTest.testNoGroupAcl

[ https://issues.apache.org/jira/browse/KAFKA-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-2910: -- Fix Version/s: (was: 0.10.1.0) 0.10.0.0 > Failure in kafka.api.SslEndToEn

Re: [VOTE] 0.10.0.0 RC1

Hi Gwen, KIP-47 is voted and passed, but not merged yet. It is actually depending on KIP-33 which is in the voting process. I know we discussed on the KIP hangout that we will do KIP-33 post 0.10.0. But since 0.10.0 is delayed, maybe we can include KIP-33 given it is a long-wanted fix by many use

[DISCUSS] KIP-52 - Add Connector Control APIs

Hi All, I've written a short KIP to add control APIs to Kafka Connect to make administration easier: https://cwiki.apache.org/confluence/display/KAFKA/KIP-52%3A+Connector+Control+APIs. Please let me know your thoughts. Thanks, Jason

[jira] [Updated] (KAFKA-3205) Error in I/O with host (java.io.EOFException) raised in producer

[ https://issues.apache.org/jira/browse/KAFKA-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3205: --- Fix Version/s: 0.10.0.0 > Error in I/O with host (java.io.EOFException) raised in producer > -

[GitHub] kafka pull request: KAFKA-3451: Add basic HTML coverage report gen...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1121 --- 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] [Updated] (KAFKA-3451) Add basic HTML coverage report generation to gradle

[ https://issues.apache.org/jira/browse/KAFKA-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3451: Resolution: Fixed Fix Version/s: 0.10.0.0 Status: Resolved (was: Patch Available)

[jira] [Commented] (KAFKA-3451) Add basic HTML coverage report generation to gradle

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

Re: [VOTE] 0.10.0.0 RC1

I'd LOVE to have KIP-33 get it. Can you work with Jun to make sure the timing will work? On Thu, Mar 31, 2016 at 9:20 AM, Becket Qin wrote: > Hi Gwen, > > KIP-47 is voted and passed, but not merged yet. It is actually depending on > KIP-33 which is in the voting process. > > I know we discussed

[jira] [Commented] (KAFKA-3488) commitAsync() fails if metadata update creates new SASL/SSL connection

[ https://issues.apache.org/jira/browse/KAFKA-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220272#comment-15220272 ] Jason Gustafson commented on KAFKA-3488: This has come up a few times in slightly

[jira] [Commented] (KAFKA-3334) First message on new topic not actually being sent, no exception thrown

[ https://issues.apache.org/jira/browse/KAFKA-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220277#comment-15220277 ] Aleksandar Stojadinovic commented on KAFKA-3334: I agree about overexposin

[jira] [Commented] (KAFKA-3334) First message on new topic not actually being sent, no exception thrown

[ https://issues.apache.org/jira/browse/KAFKA-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220289#comment-15220289 ] Ashish K Singh commented on KAFKA-3334: --- Thanks for the response [~salex89]. I will

Re: [VOTE] 0.10.0.0 RC1

Sure, do we have a new intended release close date? On Thu, Mar 31, 2016 at 10:23 AM, Gwen Shapira wrote: > I'd LOVE to have KIP-33 get it. > > Can you work with Jun to make sure the timing will work? > > On Thu, Mar 31, 2016 at 9:20 AM, Becket Qin wrote: > > > Hi Gwen, > > > > KIP-47 is voted

Re: [VOTE] 0.10.0.0 RC1

Good question :) Lets say we want: KIP-43, KIP-35, KIP-4-metadata and KIP-33 to get in. How much time do we need? I think 2 or 3 weeks is reasonable? Am I being too optimistic again? Gwen On Thu, Mar 31, 2016 at 10:42 AM, Becket Qin wrote: > Sure, do we have a new intended release close date

[jira] [Commented] (KAFKA-3205) Error in I/O with host (java.io.EOFException) raised in producer

[ https://issues.apache.org/jira/browse/KAFKA-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220339#comment-15220339 ] Flavio Junqueira commented on KAFKA-3205: - [~bondj] I've commented on the pull req

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

See Changes: [cshapi] KAFKA-3451: Add basic HTML coverage report generation to gradle -- [...truncated 1565 lines...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[17] PASSED kafk

[jira] [Commented] (KAFKA-3469) kafka-topics lock down znodes with user principal when zk security is enabled.

[ https://issues.apache.org/jira/browse/KAFKA-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220360#comment-15220360 ] Ashish K Singh commented on KAFKA-3469: --- [~fpj] pinging again for your feedback. >

[jira] [Commented] (KAFKA-3488) commitAsync() fails if metadata update creates new SASL/SSL connection

[ https://issues.apache.org/jira/browse/KAFKA-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220416#comment-15220416 ] Rajini Sivaram commented on KAFKA-3488: --- [~hachikuji] Thank you for the feedback. I

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

See Changes: [cshapi] KAFKA-3451: Add basic HTML coverage report generation to gradle -- [...truncated 1600 lines...] kafka.log.LogTest > testTruncateTo PASSED kafka.log.LogTest > testCleanShu

Re: KIP-4 Wiki Update

Looking for some resolution on the "No Topics" change. I am thinking that using null in the protocol isn't that complex, and it avoids various edge cases with having multiple fields. That leaves us with 2 options: - A: null = no topics, empty = all topics - B: null = all topics, empty = no

[jira] [Commented] (KAFKA-3334) First message on new topic not actually being sent, no exception thrown

[ https://issues.apache.org/jira/browse/KAFKA-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220604#comment-15220604 ] Jiangjie Qin commented on KAFKA-3334: - [~singhashish] I think we are on the same page

[jira] [Comment Edited] (KAFKA-3334) First message on new topic not actually being sent, no exception thrown

[ https://issues.apache.org/jira/browse/KAFKA-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220604#comment-15220604 ] Jiangjie Qin edited comment on KAFKA-3334 at 3/31/16 8:21 PM: --

Re: KIP-4 Wiki Update

I prefer B, the fact that we version the protocol means that we can fix mistakes instead of living with them forever. We should take advantage of that. Ismael On Thu, Mar 31, 2016 at 9:15 PM, Grant Henke wrote: > Looking for some resolution on the "No Topics" change. > > I am thinking that usin

Re: [VOTE] 0.10.0.0 RC1

I am not sure about the other KIPs, For KIP-33 and KIP-47 I think it is enough if we have reasonable review iterations. On Thu, Mar 31, 2016 at 10:54 AM, Gwen Shapira wrote: > Good question :) > > Lets say we want: > KIP-43, KIP-35, KIP-4-metadata and KIP-33 to get in. How much time do we > need

[GitHub] kafka pull request: KAFKA-1981 Make log compaction point configura...

Github user ewasserman closed the pull request at: https://github.com/apache/kafka/pull/1168 --- 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

[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=15220689#comment-15220689 ] ASF GitHub Bot commented on KAFKA-1981: --- Github user ewasserman closed the pull requ

[GitHub] kafka pull request: KAFKA-1981 Make log compaction point configura...

GitHub user ewasserman reopened a pull request: https://github.com/apache/kafka/pull/1168 KAFKA-1981 Make log compaction point configurable @jkreps Implements control over the portion of the head of the log that will not be compacted (i.e. preserved in detail). T

[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=15220691#comment-15220691 ] ASF GitHub Bot commented on KAFKA-1981: --- GitHub user ewasserman reopened a pull requ

Re: [DISCUSS] KIP-35 - Retrieve protocol version

Bumping this thread. I talked with Ashish and Magnus about this KIP offline and I'm gradually coming over. The new API actually stands by itself outside of the discussion about whether the client should support backwards compatibility or not. For the Java client, we could continue to support the cu

Re: [DISCUSS] KIP-35 - Retrieve protocol version

I agree with Jason. The blocking factor has been how to use the proposed changes in java client without making it super complicated. With Jason's suggestion we can get past this blocker, while keeping the core of the proposal intact. On Thu, Mar 31, 2016 at 2:51 PM, Jason Gustafson wrote: > Bum

Jira

Hi, I was browsing Kafka JIRAs and realized, that I cannot assign JIRAs to myself. Can anyone give me credentials for this, please? username: mjsax Thanks. :) -Matthias signature.asc Description: OpenPGP digital signature

Re: [VOTE] KIP-50 - Enhance Authorizer interface to be aware of supported Principal Types

+1 Thanks Parth On Wed, Mar 30, 2016 at 8:22 PM, Ewen Cheslack-Postava wrote: > +1 > > -Ewen > > On Wed, Mar 30, 2016 at 7:20 PM, Gwen Shapira wrote: > > > So my +1 is back :) > > > > On Wed, Mar 30, 2016 at 4:51 PM, Ashish Singh > wrote: > > > > > My bad, I moved the config option to rejecte

[GitHub] kafka pull request: [Minor]: Clean up of SourceTaskOffsetCommiter

GitHub user Ishiihara opened a pull request: https://github.com/apache/kafka/pull/1170 [Minor]: Clean up of SourceTaskOffsetCommiter You can merge this pull request into a Git repository by running: $ git pull https://github.com/Ishiihara/kafka minor-cleanup Alternatively you

Re: KIP-4 Wiki Update

I also prefer B. In addition to being intuitive, it seems less error-prone in the long term, though it might be a little annoying for clients maintaining backwards compatibility. -Jason On Thu, Mar 31, 2016 at 1:24 PM, Ismael Juma wrote: > I prefer B, the fact that we version the protocol means

Re: Jira

Mattias, Just added you to the contributor list. Thanks, Jun On Thu, Mar 31, 2016 at 3:44 PM, Matthias J. Sax wrote: > Hi, > > I was browsing Kafka JIRAs and realized, that I cannot assign JIRAs to > myself. Can anyone give me credentials for this, please? > > username: mjsax > > Thanks. :) >

[jira] [Commented] (KAFKA-3338) Add print and writeAsText functions to the Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220957#comment-15220957 ] Bill Bejeck commented on KAFKA-3338: I'm wondering if we need to provide a Serde for t

Re: KIP-4 Wiki Update

I have update the wiki and patch based on the feedback on the metadata changes. Please take a look and let me know if there are any concerns or issues. - Wiki: https://cwiki.apache.org/confluence/display/KAFKA/KIP-4+-+Command+line+and+centralized+administrative+operations#KIP-4-Commandline

[jira] [Commented] (KAFKA-3469) kafka-topics lock down znodes with user principal when zk security is enabled.

[ https://issues.apache.org/jira/browse/KAFKA-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221262#comment-15221262 ] Flavio Junqueira commented on KAFKA-3469: - [~singhashish] I'm sorry, I missed the