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

I am not saying that the developer at Example Inc. would develop a Login implementation that combines Smartcard and Kerberos because Retailer uses both. I am saying that Example Inc develops the LoginModule (similar to JVM security providers developing Kerberos modules). But there is no standard in

[jira] [Created] (KAFKA-3357) Update to Scala 2.11.8

Ismael Juma created KAFKA-3357: -- Summary: Update to Scala 2.11.8 Key: KAFKA-3357 URL: https://issues.apache.org/jira/browse/KAFKA-3357 Project: Kafka Issue Type: Bug Components: build

[jira] [Commented] (KAFKA-3357) Update to Scala 2.11.8

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

[GitHub] kafka pull request: KAFKA-3357; Update to Scala 2.11.8

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1032 KAFKA-3357; Update to Scala 2.11.8 Scala 2.11.8 has been released with a number of bug fixes: * http://www.scala-lang.org/news/2.11.8/ There are a few important collection fixes: * htt

[jira] [Updated] (KAFKA-3357) Update to Scala 2.11.8

[ https://issues.apache.org/jira/browse/KAFKA-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3357: --- Reviewer: Gwen Shapira Status: Patch Available (was: Open) > Update to Scala 2.11.8 > -

[jira] [Created] (KAFKA-3358) Only request metadata updates once we have a topic or a pattern subscription

Ismael Juma created KAFKA-3358: -- Summary: Only request metadata updates once we have a topic or a pattern subscription Key: KAFKA-3358 URL: https://issues.apache.org/jira/browse/KAFKA-3358 Project: Kafka

[jira] [Updated] (KAFKA-3358) Only request metadata updates once we have topics or a pattern subscription

[ https://issues.apache.org/jira/browse/KAFKA-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3358: --- Summary: Only request metadata updates once we have topics or a pattern subscription (was: Only reque

[GitHub] kafka pull request: KAFKA-3358; Only request metadata updates once...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1033 KAFKA-3358; Only request metadata updates once we have topics or a pattern subscription You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kaf

[jira] [Commented] (KAFKA-3358) Only request metadata updates once we have topics or a pattern subscription

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

[jira] [Updated] (KAFKA-3358) Only request metadata updates once we have topics or a pattern subscription

[ https://issues.apache.org/jira/browse/KAFKA-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3358: --- Status: Patch Available (was: Open) > Only request metadata updates once we have topics or a pattern

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

[ https://issues.apache.org/jira/browse/KAFKA-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2832: --- Priority: Blocker (was: Major) > support exclude.internal.topics in new consumer > --

[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=15186852#comment-15186852 ] Ismael Juma commented on KAFKA-2832: Tentatively marking this as "Blocker" for now as

[jira] [Comment Edited] (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=15186852#comment-15186852 ] Ismael Juma edited comment on KAFKA-2832 at 3/9/16 9:41 AM: Te

[jira] [Updated] (KAFKA-2960) DelayedProduce may cause message lose during repeatly leader change

[ https://issues.apache.org/jira/browse/KAFKA-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2960: --- Priority: Critical (was: Major) > DelayedProduce may cause message lose during repeatly leader change

[jira] [Updated] (KAFKA-2960) DelayedProduce may cause message loss during repeatly leader change

[ https://issues.apache.org/jira/browse/KAFKA-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2960: --- Summary: DelayedProduce may cause message loss during repeatly leader change (was: DelayedProduce may

[jira] [Updated] (KAFKA-2960) DelayedProduce may cause message loss during repeated leader change

[ https://issues.apache.org/jira/browse/KAFKA-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2960: --- Summary: DelayedProduce may cause message loss during repeated leader change (was: DelayedProduce may

[GitHub] kafka pull request: KAFKA-3358; Only request metadata updates once...

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

[jira] [Commented] (KAFKA-3358) Only request metadata updates once we have topics or a pattern subscription

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

[jira] [Updated] (KAFKA-3358) Only request metadata updates once we have topics or a pattern subscription

[ https://issues.apache.org/jira/browse/KAFKA-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3358: --- Status: Open (was: Patch Available) > Only request metadata updates once we have topics or a pattern

[GitHub] kafka pull request: MINOR: Update gradlew.bat as per latest gradle...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1034 MINOR: Update gradlew.bat as per latest gradle release When invoking `gradle` on a recent version, it updates `gradlew.bat` to fix a typo. It's an annoyance at development time as it causes a diff on

[jira] [Commented] (KAFKA-3173) Error while moving some partitions to OnlinePartition state

[ https://issues.apache.org/jira/browse/KAFKA-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186928#comment-15186928 ] Flavio Junqueira commented on KAFKA-3173: - There is a race in the controller failo

[jira] [Commented] (KAFKA-3173) Error while moving some partitions to OnlinePartition state

[ https://issues.apache.org/jira/browse/KAFKA-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186937#comment-15186937 ] Ismael Juma commented on KAFKA-3173: Sounds good [~fpj] > Error while moving some par

[GitHub] kafka pull request: Parallel log-recovery of un-flushed segments o...

GitHub user vamsi-subhash opened a pull request: https://github.com/apache/kafka/pull/1035 Parallel log-recovery of un-flushed segments on startup Did not find any tests for the method. Will be adding them You can merge this pull request into a Git repository by running: $ git

[jira] [Created] (KAFKA-3359) Parallel log-recovery of un-flushed segments on startup

Vamsi Subhash Achanta created KAFKA-3359: Summary: Parallel log-recovery of un-flushed segments on startup Key: KAFKA-3359 URL: https://issues.apache.org/jira/browse/KAFKA-3359 Project: Kafka

[jira] [Updated] (KAFKA-3359) Parallel log-recovery of un-flushed segments on startup

[ https://issues.apache.org/jira/browse/KAFKA-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsi Subhash Achanta updated KAFKA-3359: - Issue Type: Improvement (was: Bug) > Parallel log-recovery of un-flushed segments

Re: Protocol Documentation WIP

Ewen, I am okay with that. I agree something is better than nothing. I can touch up the patch today and open some jiras to track future work. Thanks, Grant On Wed, Mar 9, 2016 at 1:50 AM, Ewen Cheslack-Postava wrote: > Agreed w/ Jay's comment on the PR that this is a great idea. What if we > i

[jira] [Commented] (KAFKA-3173) Error while moving some partitions to OnlinePartition state

[ https://issues.apache.org/jira/browse/KAFKA-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187230#comment-15187230 ] Flavio Junqueira commented on KAFKA-3173: - I actually can't reorder it like that,

[jira] [Commented] (KAFKA-3296) All consumer reads hang indefinately

[ https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187284#comment-15187284 ] Simon Cooper commented on KAFKA-3296: - Are the logs useful? We've also started seeing

[jira] [Comment Edited] (KAFKA-3296) All consumer reads hang indefinately

[ https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187284#comment-15187284 ] Simon Cooper edited comment on KAFKA-3296 at 3/9/16 4:07 PM: -

Re: [DISCUSS] KIP-30 Allow for brokers to have plug-able consensus and meta data storage sub systems

Imagine a small team with very limited budget and operational capacity that wants to use Kafka, and needs coordination service for other things too (e.g. service discovery). It's limiting choices too hard to just ZooKeeper if Kafka supports ZooKeeper only. It would be better if Kafka's preferred ch

[jira] [Created] (KAFKA-3360) Add a protocol page/section to the official Kafka documentation

Grant Henke created KAFKA-3360: -- Summary: Add a protocol page/section to the official Kafka documentation Key: KAFKA-3360 URL: https://issues.apache.org/jira/browse/KAFKA-3360 Project: Kafka Is

[jira] [Created] (KAFKA-3361) Initial protocol documentation page and generation

Grant Henke created KAFKA-3361: -- Summary: Initial protocol documentation page and generation Key: KAFKA-3361 URL: https://issues.apache.org/jira/browse/KAFKA-3361 Project: Kafka Issue Type: Sub-

Re: [GitHub] kafka pull request: Parallel log-recovery of un-flushed segments o...

Hi all, https://github.com/apache/kafka/pull/1035 This pull request will make the log-segment load parallel with two configurable properties "log.recovery.threads" and " log.recovery.max.interval.ms". On startup, currently the log segments within a logDir are loaded sequentially when there is a u

[jira] [Created] (KAFKA-3363) Add a documentation field for schemas and update doc generation

Grant Henke created KAFKA-3363: -- Summary: Add a documentation field for schemas and update doc generation Key: KAFKA-3363 URL: https://issues.apache.org/jira/browse/KAFKA-3363 Project: Kafka Is

[jira] [Work started] (KAFKA-3361) Initial protocol documentation page and generation

[ https://issues.apache.org/jira/browse/KAFKA-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3361 started by Grant Henke. -- > Initial protocol documentation page and generation > --

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

Grant Henke created KAFKA-3362: -- Summary: Update protocol schema and field doc strings Key: KAFKA-3362 URL: https://issues.apache.org/jira/browse/KAFKA-3362 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-3364) Centrallize doc generation and move all generated docs under a single "generated" folder

Grant Henke created KAFKA-3364: -- Summary: Centrallize doc generation and move all generated docs under a single "generated" folder Key: KAFKA-3364 URL: https://issues.apache.org/jira/browse/KAFKA-3364 Pr

[GitHub] kafka pull request: MINOR: Update gradlew.bat as per latest gradle...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1034 --- 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-3358) Only request metadata updates once we have topics or a pattern subscription

[ https://issues.apache.org/jira/browse/KAFKA-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3358: --- Assignee: Jason Gustafson (was: Ismael Juma) > Only request metadata updates once we have topics or a

[GitHub] kafka pull request: KAFKA-3318: clean up consumer logging and erro...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1036 KAFKA-3318: clean up consumer logging and error messages You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-3318 Alternati

[jira] [Commented] (KAFKA-3318) Improve consumer rebalance error messaging

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

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

See Changes: [me] MINOR: Update gradlew.bat as per latest gradle release -- [...truncated 66 lines...]

[jira] [Assigned] (KAFKA-2370) Add pause/unpause connector support

[ https://issues.apache.org/jira/browse/KAFKA-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-2370: -- Assignee: Jason Gustafson (was: Ewen Cheslack-Postava) > Add pause/unpause connector s

[jira] [Created] (KAFKA-3365) Add a documentation field for types and update doc generation

Grant Henke created KAFKA-3365: -- Summary: Add a documentation field for types and update doc generation Key: KAFKA-3365 URL: https://issues.apache.org/jira/browse/KAFKA-3365 Project: Kafka Issu

[jira] [Updated] (KAFKA-3365) Add a documentation field for types and update doc generation

[ https://issues.apache.org/jira/browse/KAFKA-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3365: --- Description: Currently the type class does not allow a documentation field. This means we can't auto

[jira] [Created] (KAFKA-3366) Find a way to auto-generate expected error codes

Grant Henke created KAFKA-3366: -- Summary: Find a way to auto-generate expected error codes Key: KAFKA-3366 URL: https://issues.apache.org/jira/browse/KAFKA-3366 Project: Kafka Issue Type: Sub-ta

[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=15187652#comment-15187652 ] Ashish K Singh commented on KAFKA-2982: --- [~ijuma] should we update the tools to use

[jira] [Comment Edited] (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=15187652#comment-15187652 ] Ashish K Singh edited comment on KAFKA-2982 at 3/9/16 6:54 PM: -

[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=15187692#comment-15187692 ] Ismael Juma commented on KAFKA-2982: Which tools did you have in mind [~singhashish]?

[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=15187757#comment-15187757 ] Ashish K Singh commented on KAFKA-2982: --- [~ijuma] following tools rely on `kafka.pro

[jira] [Created] (KAFKA-3368) Add the Message/Record set protocol to the protocol docs

Grant Henke created KAFKA-3368: -- Summary: Add the Message/Record set protocol to the protocol docs Key: KAFKA-3368 URL: https://issues.apache.org/jira/browse/KAFKA-3368 Project: Kafka Issue Type

[jira] [Created] (KAFKA-3367) Delete topic dont delete the complete log from kafka

Akshath Patkar created KAFKA-3367: - Summary: Delete topic dont delete the complete log from kafka Key: KAFKA-3367 URL: https://issues.apache.org/jira/browse/KAFKA-3367 Project: Kafka Issue Ty

[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=15187764#comment-15187764 ] Ismael Juma commented on KAFKA-2982: [~singhashish], We should move non-deprecated too

[VOTE] KIP-47 - Add timestamp-based log deletion policy

Hello, I'd like to initiate the vote for KIP-47. Thanks, Bill Warshaw

[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=15187795#comment-15187795 ] Ashish K Singh commented on KAFKA-2982: --- [~ijuma] makes sense. Just wanted to get a

[jira] [Assigned] (KAFKA-3355) GetOffsetShell command doesn't work with SASL enabled Kafka

[ https://issues.apache.org/jira/browse/KAFKA-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh reassigned KAFKA-3355: - Assignee: Ashish K Singh > GetOffsetShell command doesn't work with SASL enabled Kafka >

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

+1 (binding) On Tue, Mar 8, 2016, at 02:37 AM, tao xiao wrote: > +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,

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

Why we need to add this additional method just for validation. This will invalidate all the existing authorizer implementations. Why can't we add the logic for validation and pass it as authorizer config. -Harsha On Mon, Mar 7, 2016, at 04:33 PM, Ashish Singh wrote: > + Parth, Harsha > > On Mon

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

See Changes: [me] MINOR: Update gradlew.bat as per latest gradle release -- [...truncated 2789 lines...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[16] PASSED kafka.log.BrokerC

[jira] [Updated] (KAFKA-3361) Initial protocol documentation page and generation

[ https://issues.apache.org/jira/browse/KAFKA-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3361: --- Status: Patch Available (was: In Progress) > Initial protocol documentation page and generation > ---

[jira] [Commented] (KAFKA-3361) Initial protocol documentation page and generation

[ https://issues.apache.org/jira/browse/KAFKA-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187848#comment-15187848 ] Grant Henke commented on KAFKA-3361: Pull request available here: https://github.com/a

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

Hi Harsha, On Wed, Mar 9, 2016 at 12:04 PM, Harsha wrote: > Why we need to add this additional method just for validation. This will > invalidate all the existing authorizer implementations. As PrincipalTypes is implementation specific, wouldn't it be required for users to know what principal t

[jira] [Updated] (KAFKA-3344) Remove previous system test's leftover test-log4j.properties

[ https://issues.apache.org/jira/browse/KAFKA-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3344: -- Fix Version/s: 0.10.0.0 > Remove previous system test's leftover test-log4j.properties > ---

[jira] [Updated] (KAFKA-3344) Remove previous system test's leftover test-log4j.properties

[ https://issues.apache.org/jira/browse/KAFKA-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3344: -- Affects Version/s: 0.9.0.1 > Remove previous system test's leftover test-log4j.properties >

[jira] [Updated] (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:all-tabpanel ] Ashish K Singh updated KAFKA-3334: -- Fix Version/s: 0.10.0.0 Status: Patch Available (was: Open) > First message on new t

[jira] [Updated] (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:all-tabpanel ] Ashish K Singh updated KAFKA-3331: -- Fix Version/s: 0.10.1.0 > Refactor TopicCommand to make it testable and add unit tests > ---

[jira] [Updated] (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:all-tabpanel ] Ashish K Singh updated KAFKA-3331: -- Affects Version/s: 0.9.0.1 > Refactor TopicCommand to make it testable and add unit tests >

[jira] [Updated] (KAFKA-3247) kafka-topic tool can use an option to see just "unbalanced partitions"

[ https://issues.apache.org/jira/browse/KAFKA-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3247: -- Fix Version/s: 0.10.0.0 > kafka-topic tool can use an option to see just "unbalanced partitions"

[jira] [Created] (KAFKA-3369) Add unit-tests to the Metadata Cache

Gwen Shapira created KAFKA-3369: --- Summary: Add unit-tests to the Metadata Cache Key: KAFKA-3369 URL: https://issues.apache.org/jira/browse/KAFKA-3369 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-3369) Add unit-tests to the Metadata Cache

[ https://issues.apache.org/jira/browse/KAFKA-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188040#comment-15188040 ] Grant Henke commented on KAFKA-3369: [~gwenshap] The [pull request| https://github.com

[jira] [Commented] (KAFKA-3369) Add unit-tests to the Metadata Cache

[ https://issues.apache.org/jira/browse/KAFKA-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188053#comment-15188053 ] Gwen Shapira commented on KAFKA-3369: - I'll check after reviewing the PR and perhaps c

[jira] [Created] (KAFKA-3370) Add options to auto.offset.reset to reset offsets upon initialization only

Guozhang Wang created KAFKA-3370: Summary: Add options to auto.offset.reset to reset offsets upon initialization only Key: KAFKA-3370 URL: https://issues.apache.org/jira/browse/KAFKA-3370 Project: Kaf

[jira] [Commented] (KAFKA-3352) Avoid DNS reverse lookups

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

[GitHub] kafka pull request: KAFKA-3352: Avoid DNS reverse lookups

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1030 --- 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-3352) Avoid DNS reverse lookups

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

[jira] [Commented] (KAFKA-3370) Add options to auto.offset.reset to reset offsets upon initialization only

[ https://issues.apache.org/jira/browse/KAFKA-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188181#comment-15188181 ] Cody Koeninger commented on KAFKA-3370: --- So would case 1 also include addition of an

[jira] [Commented] (KAFKA-3355) GetOffsetShell command doesn't work with SASL enabled Kafka

[ https://issues.apache.org/jira/browse/KAFKA-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188187#comment-15188187 ] Gwen Shapira commented on KAFKA-3355: - If you think you will finish by 0.10.0, go for

[jira] [Comment Edited] (KAFKA-3355) GetOffsetShell command doesn't work with SASL enabled Kafka

[ https://issues.apache.org/jira/browse/KAFKA-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188187#comment-15188187 ] Gwen Shapira edited comment on KAFKA-3355 at 3/9/16 10:28 PM: --

[jira] [Resolved] (KAFKA-3354) Streams system tests fail in trunk

[ https://issues.apache.org/jira/browse/KAFKA-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-3354. - Resolution: Fixed Assignee: Guozhang Wang > Streams system tests fail in trunk > ---

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

See Changes: [cshapi] KAFKA-3352: Avoid DNS reverse lookups -- [...truncated 1509 lines...] kafka.log.LogTest > testTimeBasedLogRoll PASSED kafka.log.LogTest > testLoadEmptyLog PASSED kafka.lo

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

See

Re: [VOTE] KIP-47 - Add timestamp-based log deletion policy

For convenience, the KIP is here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-47+-+Add+timestamp-based+log+deletion+policy Do you mind updating the KIP with time formats we plan on supporting in the configuration? On Wed, Mar 9, 2016 at 11:44 AM, Bill Warshaw wrote: > Hello, > > I'd l

[jira] [Updated] (KAFKA-3357) Update to Scala 2.11.8

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

[GitHub] kafka pull request: KAFKA-3357; Update to Scala 2.11.8

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1032 --- 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-3357) Update to Scala 2.11.8

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

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

What I'm hearing is that: 1. In order to support authentication mechanisms that were not written specifically with Kafka in mind, someone will need to write the integration between the mechanism and Kafka. This may include Login and CallbackHandler classes. This can be the mechanism vendor, the us

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

Harsha, Since you are clearly in favor of the KIP, do you mind jumping into the discussion thread and help me understand the decision behind the configuration parameters only allowing a single Login and CallbackHandler class? This seems too limiting to me, and while Rajini is trying hard to convin

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

See Changes: [cshapi] KAFKA-3357; Update to Scala 2.11.8 -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-us1 (Ubuntu ubuntu ubuntu-us) in

Re: Protocol Documentation WIP

Hey Ewen, For "its own page" which location are you specifically thinking about? Guozhang On Wed, Mar 9, 2016 at 6:48 AM, Grant Henke wrote: > Ewen, > > I am okay with that. I agree something is better than nothing. I can touch > up the patch today and open some jiras to track future work. > >

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

See Changes: [cshapi] KAFKA-3357; Update to Scala 2.11.8 -- [...truncated 2969 lines...] kafka.log.LogTest > testTimeBasedLogRollJitter PASSED kafka.log.LogTest > testParseTopicPartitionName PA

Re: Protocol Documentation WIP

FYI. I have updated the pull request here: https://github.com/apache/kafka/pull/970 On Wed, Mar 9, 2016 at 10:18 PM, Guozhang Wang wrote: > Hey Ewen, > > For "its own page" which location are you specifically thinking about? > > Guozhang > > On Wed, Mar 9, 2016 at 6:48 AM, Grant Henke wrote:

[jira] [Commented] (KAFKA-3370) Add options to auto.offset.reset to reset offsets upon initialization only

[ https://issues.apache.org/jira/browse/KAFKA-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188662#comment-15188662 ] Guozhang Wang commented on KAFKA-3370: -- Yes, that should be falling in case 1) too.

[jira] [Commented] (KAFKA-3361) Initial protocol documentation page and generation

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

[GitHub] kafka pull request: KAFKA-3361: Initial protocol documentation pag...

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

[GitHub] kafka pull request: MINOR: KAFKA-3361 follow up

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/1037 MINOR: KAFKA-3361 follow up You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/kafka protocol-minor Alternatively you can review and

[jira] [Commented] (KAFKA-3361) Initial protocol documentation page and generation

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

[GitHub] kafka pull request: KAFKA-3361: Initial protocol documentation pag...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/1038 KAFKA-3361: Initial protocol documentation page and generation (0.9) - Moves all generated docs under /docs/generated - Generates docs for Protocol, Errors, and ApiKeys - Adds new protocol

[jira] [Commented] (KAFKA-3361) Initial protocol documentation page and generation

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

[GitHub] kafka pull request: MINOR: KAFKA-3361 follow up

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1037 --- 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-3361) Initial protocol documentation page and generation

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

  1   2   >