Re: [DISCUSS] KIP-43: Kafka SASL enhancements

Yes, I understand that. However, because the current configuration only allows a single callback and a single login module, I need to supply a class that supports callbacks or logins for every single mechanism that I need to support. I question whether this is applicable in real-world scenario whe

Re: [VOTE] Release plan - Kafka 0.10.0

+1 (non-binding). I will review and update any jiras I think should be tracked today. Gwen the release tracking page is awesome! +1 (non-binding) One clarification: there are currently 11 issues marked as blockers, is that an accurate list? http://bit.ly/21YCthZ -Flavio > On 08 Mar 2016, at

[jira] [Updated] (KAFKA-3351) Kafka Connect Rest restarts all connectors on POST or DELETE

[ https://issues.apache.org/jira/browse/KAFKA-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3351: Reviewer: Gwen Shapira Fix Version/s: 0.10.0.0 > Kafka Connect Rest restarts all connectors

[jira] [Updated] (KAFKA-3047) Explicit offset assignment in Log.append can corrupt the log

[ https://issues.apache.org/jira/browse/KAFKA-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3047: Priority: Blocker (was: Major) > Explicit offset assignment in Log.append can corrupt the log > ---

[jira] [Updated] (KAFKA-2024) Cleaner can generate unindexable log segments

[ https://issues.apache.org/jira/browse/KAFKA-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2024: Fix Version/s: 0.9.0.0 > Cleaner can generate unindexable log segments > ---

[jira] [Commented] (KAFKA-2163) Offsets manager cache should prevent stale-offset-cleanup while an offset load is in progress; otherwise we can lose consumer offsets

[ https://issues.apache.org/jira/browse/KAFKA-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185164#comment-15185164 ] Gwen Shapira commented on KAFKA-2163: - We are no longer merging into 0.8.2 branch beca

[jira] [Updated] (KAFKA-3351) Kafka Connect Rest restarts all connectors on POST or DELETE

[ https://issues.apache.org/jira/browse/KAFKA-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3351: Assignee: Jason Gustafson (was: Ewen Cheslack-Postava) > Kafka Connect Rest restarts all connectors

Re: [VOTE] Release plan - Kafka 0.10.0

For a certain definition of accurate :) We can add blockers as we find critical bugs and we can remove items if they become less relevant. As we get closer to rolling out the release candidate, we can re-evaluate the remaining blockers and re-consider whether they indeed prevent us from voting a r

[jira] [Updated] (KAFKA-3097) Acls for PrincipalType User are case sensitive

[ https://issues.apache.org/jira/browse/KAFKA-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3097: --- Fix Version/s: 0.10.0.0 > Acls for PrincipalType User are case sensitive > ---

[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 ] Grant Henke resolved KAFKA-3112. Resolution: Duplicate > One incorrect bootstrap server will prevent Kafka producer from opening > --

[jira] [Resolved] (KAFKA-3099) Please update A+Guide+To+The+Kafka+Protocol Wiki

[ https://issues.apache.org/jira/browse/KAFKA-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KAFKA-3099. Resolution: Duplicate > Please update A+Guide+To+The+Kafka+Protocol Wiki > -

[jira] [Updated] (KAFKA-3219) Long topic names mess up broker topic state

[ https://issues.apache.org/jira/browse/KAFKA-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3219: --- Fix Version/s: 0.10.0.0 > Long topic names mess up broker topic state > --

[jira] [Updated] (KAFKA-3252) compression type for a topic should be used during log compaction

[ https://issues.apache.org/jira/browse/KAFKA-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3252: --- Fix Version/s: 0.10.0.0 > compression type for a topic should be used during log compaction > ---

[jira] [Updated] (KAFKA-3244) TopicCommand doesn't allow to add partitions with specific assignment

[ https://issues.apache.org/jira/browse/KAFKA-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3244: --- Assignee: (was: Grant Henke) > TopicCommand doesn't allow to add partitions with specific assignme

[jira] [Updated] (KAFKA-3258) BrokerTopicMetrics of deleted topics are never deleted

[ https://issues.apache.org/jira/browse/KAFKA-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3258: --- Fix Version/s: 0.10.0.0 > BrokerTopicMetrics of deleted topics are never deleted > ---

[jira] [Commented] (KAFKA-2832) support exclude.internal.topics in new consumer

[ https://issues.apache.org/jira/browse/KAFKA-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185135#comment-15185135 ] Grant Henke commented on KAFKA-2832: In the patch review it was decided that it would

[jira] [Assigned] (KAFKA-3269) Update topic metadata request to included needed information for polling

[ https://issues.apache.org/jira/browse/KAFKA-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke reassigned KAFKA-3269: -- Assignee: Grant Henke > Update topic metadata request to included needed information for pollin

[jira] [Updated] (KAFKA-3285) Mirror Maker whitelist behavior differs between old and new consumer

[ https://issues.apache.org/jira/browse/KAFKA-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3285: --- Priority: Major (was: Minor) > Mirror Maker whitelist behavior differs between old and new consumer >

[jira] [Updated] (KAFKA-3285) Mirror Maker whitelist behavior differs between old and new consumer

[ https://issues.apache.org/jira/browse/KAFKA-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3285: --- Fix Version/s: 0.10.0.0 > Mirror Maker whitelist behavior differs between old and new consumer > -

[jira] [Commented] (KAFKA-3285) Mirror Maker whitelist behavior differs between old and new consumer

[ https://issues.apache.org/jira/browse/KAFKA-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185130#comment-15185130 ] Grant Henke commented on KAFKA-3285: I think would be resolved when KAFKA-2832 is avai

[jira] [Resolved] (KAFKA-3295) test submit jira issue

[ https://issues.apache.org/jira/browse/KAFKA-3295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KAFKA-3295. Resolution: Invalid > test submit jira issue > -- > > Key: KAFKA

[jira] [Commented] (KAFKA-3309) Update Protocol Documentation WIP patch

[ https://issues.apache.org/jira/browse/KAFKA-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185114#comment-15185114 ] Grant Henke commented on KAFKA-3309: [~singhashish] This patch is not in yet. So I may

[jira] [Resolved] (KAFKA-3350) The first published message in an autocreated topic results in an error

[ https://issues.apache.org/jira/browse/KAFKA-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KAFKA-3350. Resolution: Duplicate > The first published message in an autocreated topic results in an error > --

[jira] [Commented] (KAFKA-2982) Mark the old Scala producer and related classes as deprecated

[ https://issues.apache.org/jira/browse/KAFKA-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185085#comment-15185085 ] Grant Henke commented on KAFKA-2982: [~ijuma] Feel free to take it. > Mark the old S

[jira] [Updated] (KAFKA-2982) Mark the old Scala producer and related classes as deprecated

[ https://issues.apache.org/jira/browse/KAFKA-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-2982: --- Assignee: Ismael Juma (was: Grant Henke) > Mark the old Scala producer and related classes as depreca

[jira] [Created] (KAFKA-3351) Kafka Connect Rest restarts all connectors on POST or DELETE

Andrew Stevenson created KAFKA-3351: --- Summary: Kafka Connect Rest restarts all connectors on POST or DELETE Key: KAFKA-3351 URL: https://issues.apache.org/jira/browse/KAFKA-3351 Project: Kafka

[jira] [Commented] (KAFKA-2163) Offsets manager cache should prevent stale-offset-cleanup while an offset load is in progress; otherwise we can lose consumer offsets

[ https://issues.apache.org/jira/browse/KAFKA-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185020#comment-15185020 ] Vamsi Subhash Achanta commented on KAFKA-2163: -- Can this be merged into 0.8.2

[jira] [Created] (KAFKA-3350) The first published message in an autocreated topic results in an error

Jasper Siepkes created KAFKA-3350: - Summary: The first published message in an autocreated topic results in an error Key: KAFKA-3350 URL: https://issues.apache.org/jira/browse/KAFKA-3350 Project: Kafk

[jira] [Commented] (KAFKA-3323) Negative offsets in Log Segment Index files due to Integer overflow when compaction is enabled

[ https://issues.apache.org/jira/browse/KAFKA-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184801#comment-15184801 ] Ismael Juma commented on KAFKA-3323: [~michael.schiff], do you agree that this is a du

[jira] [Comment Edited] (KAFKA-3323) Negative offsets in Log Segment Index files due to Integer overflow when compaction is enabled

[ https://issues.apache.org/jira/browse/KAFKA-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184801#comment-15184801 ] Ismael Juma edited comment on KAFKA-3323 at 3/8/16 11:26 AM: -

[jira] [Commented] (KAFKA-3202) Add system test for KIP-31 and KIP-32 - Change message format version on the fly

[ https://issues.apache.org/jira/browse/KAFKA-3202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184777#comment-15184777 ] Eno Thereska commented on KAFKA-3202: - [~apovzner][~becket_qin]I'm picking this up. >

[jira] [Assigned] (KAFKA-3202) Add system test for KIP-31 and KIP-32 - Change message format version on the fly

[ https://issues.apache.org/jira/browse/KAFKA-3202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reassigned KAFKA-3202: --- Assignee: Eno Thereska (was: Anna Povzner) > Add system test for KIP-31 and KIP-32 - Change

Re: [DISCUSS] KIP-43: Kafka SASL enhancements

Gwen, Sorry if this is not clear in the KIP. The goal of the KIP is to enable new mechanisms to be added without any changes to Apache Kafka. The configuration proposed by the KIP is based on the configurability of the Java SASL API and what it would take to add a new mechanism similar to Kerberos

Re: [VOTE] KIP-43: Kafka SASL enhancements

+1 (non-binding) On Tue, 8 Mar 2016 at 05:33 Andrew Schofield < andrew_schofield_j...@outlook.com> wrote: > +1 (non-binding) > > > > From: ism...@juma.me.uk > > Date: Mon, 7 Mar 2016 19:52:11 + > > Subject: Re: [VOTE] KIP-43: Kafka SASL enhancements >

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

See

Re: [VOTE] Release plan - Kafka 0.10.0

+1 (non-binding) One clarification: there are currently 11 issues marked as blockers, is that an accurate list? http://bit.ly/21YCthZ -Flavio > On 08 Mar 2016, at 06:12, Harsha wrote: > > > +1 > > Thanks, > Harsha > On Mon, Mar 7, 2016, at 09:49 PM, Jun Rao wrote: >> +1 >> >> Thanks, >>

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

See Changes: [me] KAFKA-3201: Added rolling upgrade system tests from 0.8 and 0.9 to 0.10 -- [...truncated 1791 lines...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[1] PASSED

[jira] [Updated] (KAFKA-3328) SimpleAclAuthorizer can lose ACLs with frequent add/remove calls

[ https://issues.apache.org/jira/browse/KAFKA-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3328: --- Status: Patch Available (was: Open) > SimpleAclAuthorizer can lose ACLs with frequent add/remove call

[jira] [Updated] (KAFKA-3328) SimpleAclAuthorizer can lose ACLs with frequent add/remove calls

[ https://issues.apache.org/jira/browse/KAFKA-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3328: --- Fix Version/s: 0.10.0.0 > SimpleAclAuthorizer can lose ACLs with frequent add/remove calls > -

[jira] [Updated] (KAFKA-3328) SimpleAclAuthorizer can lose ACLs with frequent add/remove calls

[ https://issues.apache.org/jira/browse/KAFKA-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3328: --- Priority: Critical (was: Major) > SimpleAclAuthorizer can lose ACLs with frequent add/remove calls >

[jira] [Commented] (KAFKA-3047) Explicit offset assignment in Log.append can corrupt the log

[ https://issues.apache.org/jira/browse/KAFKA-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184629#comment-15184629 ] Ismael Juma commented on KAFKA-3047: Thanks for the report and suggested fix Maciek.

[jira] [Updated] (KAFKA-3047) Explicit offset assignment in Log.append can corrupt the log

[ https://issues.apache.org/jira/browse/KAFKA-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3047: --- Reviewer: Jun Rao Status: Patch Available (was: Open) > Explicit offset assignment in Log.appen

[jira] [Commented] (KAFKA-3047) Explicit offset assignment in Log.append can corrupt the log

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

[GitHub] kafka pull request: KAFKA-3047: Explicit offset assignment in Log....

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1029 KAFKA-3047: Explicit offset assignment in Log.append can corrupt the log This fix was suggested by Maciek Makowski, who also reported the problem. You can merge this pull request into a Git repository

<    1   2