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

Hi Jason, "t. I think what you're saying is that the KafkaSpout has been compiled against the 0.9 client, but it may need to be to run against 0.10 (if the user depends on that version instead). Is that correct?" Yes thats true. " Is that correct? In general, are you expecting that

[jira] [Commented] (KAFKA-3578) Allow cross origin HTTP requests on all HTTP methods

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

[jira] [Commented] (KAFKA-1880) Add support for checking binary/source compatibility

[ https://issues.apache.org/jira/browse/KAFKA-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263372#comment-15263372 ] Grant Henke commented on KAFKA-1880: I actually did not use the compatibility checker in the current

[GitHub] kafka pull request: KAFKA-3578: Allow cross origin HTTP requests o...

GitHub user Ishiihara opened a pull request: https://github.com/apache/kafka/pull/1288 KAFKA-3578: Allow cross origin HTTP requests on all HTTP methods You can merge this pull request into a Git repository by running: $ git pull https://github.com/Ishiihara/kafka kip-56

[jira] [Commented] (KAFKA-1880) Add support for checking binary/source compatibility

[ https://issues.apache.org/jira/browse/KAFKA-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263358#comment-15263358 ] Ismael Juma commented on KAFKA-1880: That page lists a number of tools. What's the thinking around

[jira] [Commented] (KAFKA-1880) Add support for checking binary/source compatibility

[ https://issues.apache.org/jira/browse/KAFKA-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263355#comment-15263355 ] Ismael Juma commented on KAFKA-1880: This is definitely much needed. > Add support for checking

[jira] [Commented] (KAFKA-1880) Add support for checking binary/source compatibility

[ https://issues.apache.org/jira/browse/KAFKA-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263347#comment-15263347 ] Gwen Shapira commented on KAFKA-1880: - It is useful already! Thank you for this cool contribution -

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

See Changes: [ismael] MINOR: Avoid compiler warnings when registering metrics in KafkaServer [me] KAFKA-3382: Add system test for ReplicationVerificationTool -- [...truncated 1611 lines...]

Re: [DISCUSS] KIP-54 Sticky Partition Assignment Strategy

Hey Edo, The background is here: https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Client-side+Assignment+Proposal. Yes, it's more work for implementations, but it also opens the door for other use cases (e.g. Kafka Connect is using the same protocol). It also makes it easier for clients to

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

See Changes: [ismael] MINOR: Avoid compiler warnings when registering metrics in KafkaServer [me] KAFKA-3382: Add system test for ReplicationVerificationTool -- [...truncated 4839 lines...]

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

FYI. I have attached a sample clients API change/compatibility report to KAFKA-1880 . The report shows changes in the public apis between the 0.9 and trunk branches. Some of them are expected per KIP-45 obviously. Thanks, Grant On Thu, Apr 28,

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

Hey Harsha, We're just trying to understand the problem first. I think what you're saying is that the KafkaSpout has been compiled against the 0.9 client, but it may need to be to run against 0.10 (if the user depends on that version instead). Is that correct? In general, are you expecting that

[jira] [Updated] (KAFKA-1880) Add support for checking binary/source compatibility

[ https://issues.apache.org/jira/browse/KAFKA-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-1880: --- Attachment: compatibilityReport.html Attaching a sample html compatibility report for all public

[jira] [Commented] (KAFKA-1880) Add support for checking binary/source compatibility

[ https://issues.apache.org/jira/browse/KAFKA-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263239#comment-15263239 ] Grant Henke commented on KAFKA-1880: I have started hacking together a solution for this that is

[jira] [Assigned] (KAFKA-1880) Add support for checking binary/source compatibility

[ https://issues.apache.org/jira/browse/KAFKA-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke reassigned KAFKA-1880: -- Assignee: Grant Henke (was: Ashish K Singh) > Add support for checking binary/source

[jira] [Created] (KAFKA-3641) Fix RecordMetadata constructor backward compatibility

Grant Henke created KAFKA-3641: -- Summary: Fix RecordMetadata constructor backward compatibility Key: KAFKA-3641 URL: https://issues.apache.org/jira/browse/KAFKA-3641 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-54 Sticky Partition Assignment Strategy

Hi why is the calculation of the partition assignments to group member being executed by the client (leader of the group), rather than server (eg by the group Coordinator) ? This question came up working with Vahid Hashemian on https://issues.apache.org/jira/browse/KAFKA-2273 We have

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

See Changes: [ismael] KAFKA-3636; Change default max session timeout to 5 minutes -- [...truncated 1664 lines...] kafka.server.ServerStartupTest > testConflictBrokerRegistration PASSED

[jira] [Created] (KAFKA-3640) Reduce the latency of topic metadata requests

Flavio Junqueira created KAFKA-3640: --- Summary: Reduce the latency of topic metadata requests Key: KAFKA-3640 URL: https://issues.apache.org/jira/browse/KAFKA-3640 Project: Kafka Issue

[jira] [Resolved] (KAFKA-3638) Using kafka-console-producer with invalid broker list weirds to unexpected behavior

[ https://issues.apache.org/jira/browse/KAFKA-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KAFKA-3638. Resolution: Duplicate Assignee: Grant Henke > Using kafka-console-producer with invalid

[jira] [Commented] (KAFKA-2273) Add rebalance with a minimal number of reassignments to server-defined strategy list

[ https://issues.apache.org/jira/browse/KAFKA-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263195#comment-15263195 ] Edoardo Comar commented on KAFKA-2273: -- Working on this with [~vahid] - propagating the overall

[jira] [Commented] (KAFKA-3382) Add system test for ReplicationVerificationTool

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

[jira] [Updated] (KAFKA-3382) Add system test for ReplicationVerificationTool

[ https://issues.apache.org/jira/browse/KAFKA-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3382: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved

[GitHub] kafka pull request: KAFKA-3382: Add system test for ReplicationVer...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1160 --- 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-3638) Using kafka-console-producer with invalid broker list weirds to unexpected behavior

[ https://issues.apache.org/jira/browse/KAFKA-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263187#comment-15263187 ] Jarek Jarcec Cecho commented on KAFKA-3638: --- Yup KAFKA-3468 definitely seems to be describing

[GitHub] kafka pull request: MINOR: Avoid compiler warnings when registerin...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1280 --- 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] [Updated] (KAFKA-3440) Add Javadoc for KTable (changelog stream) and KStream (record stream)

[ https://issues.apache.org/jira/browse/KAFKA-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3440: --- Status: Patch Available (was: In Progress) > Add Javadoc for KTable (changelog stream) and

[jira] [Commented] (KAFKA-3440) Add Javadoc for KTable (changelog stream) and KStream (record stream)

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

[GitHub] kafka pull request: KAFKA-3440: update JavaDoc

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/1287 KAFKA-3440: update JavaDoc - add class doc for KTable, KStream, JoinWindows - add missing @return tags You can merge this pull request into a Git repository by running: $ git pull

Re: Tell us how you're using Kafka and what you'd like to see in the future

Hi Neha, Thanks for sending out this Survey! Hopefully we got a lot of responses from the community. Are there any results to share? Thank you, Grant On Wed, Apr 6, 2016 at 4:58 PM, Neha Narkhede wrote: > Folks, > > We'd like to hear from community members about how you are

Re: No Heartbeat request on commit

I sent it as attachment. I did not zip it and may have been rejected by mail server. Will send again shortly. On Apr 28, 2016 5:11 PM, "Jason Gustafson" wrote: > Hey Vinay, > > Did you forget to attach the simple class? > > -Jason > > On Thu, Apr 28, 2016 at 1:14 PM, vinay

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

See Changes: [ismael] KAFKA-3617; Unit tests for SASL authenticator -- [...truncated 4371 lines...] kafka.admin.AdminRackAwareTest > testAssignmentWithRackAwareWithUnevenReplicas PASSED

[jira] [Commented] (KAFKA-3618) Handle ApiVersionRequest before SASL handshake

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

[GitHub] kafka pull request: KAFKA-3618: Handle ApiVersionsRequest before S...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/1286 KAFKA-3618: Handle ApiVersionsRequest before SASL authentication Server-side implementation and tests for handling ApiVersionsRequest before SaslHandshakeRequest. You can merge this pull

[jira] [Created] (KAFKA-3639) Configure default serdes passed via StreamsConfig

Guozhang Wang created KAFKA-3639: Summary: Configure default serdes passed via StreamsConfig Key: KAFKA-3639 URL: https://issues.apache.org/jira/browse/KAFKA-3639 Project: Kafka Issue Type:

[GitHub] kafka pull request: KAFKA-3618: Handle ApiVersionsRequest before S...

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

[jira] [Commented] (KAFKA-3634) Add ducktape tests for upgrade with SASL

[ https://issues.apache.org/jira/browse/KAFKA-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263065#comment-15263065 ] Ismael Juma commented on KAFKA-3634: I think we may already have the first case described above, but

[jira] [Updated] (KAFKA-3515) Migrate org.apache.kafka.connect.json.JsonSerializer / Deser to common package

[ https://issues.apache.org/jira/browse/KAFKA-3515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3515: --- Fix Version/s: (was: 0.10.0.0) 0.10.1.0 > Migrate

[jira] [Created] (KAFKA-3638) Using kafka-console-producer with invalid broker list weirds to unexpected behavior

Jarek Jarcec Cecho created KAFKA-3638: - Summary: Using kafka-console-producer with invalid broker list weirds to unexpected behavior Key: KAFKA-3638 URL: https://issues.apache.org/jira/browse/KAFKA-3638

[jira] [Commented] (KAFKA-3618) Handle ApiVersionRequest before SASL handshake

[ https://issues.apache.org/jira/browse/KAFKA-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263050#comment-15263050 ] ASF GitHub Bot commented on KAFKA-3618: --- Github user rajinisivaram closed the pull request at:

[jira] [Resolved] (KAFKA-3636) Increase default group.max.session.timeout.ms to 5 minutes

[ https://issues.apache.org/jira/browse/KAFKA-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3636. Resolution: Fixed Fix Version/s: 0.10.0.0 Issue resolved by pull request 1284

[jira] [Commented] (KAFKA-3636) Increase default group.max.session.timeout.ms to 5 minutes

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

[GitHub] kafka pull request: KAFKA-3636: change default max session timeout...

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

Re: No Heartbeat request on commit

Hey Vinay, Did you forget to attach the simple class? -Jason On Thu, Apr 28, 2016 at 1:14 PM, vinay sharma wrote: > I was also wondering that if commitSync acts as heartbeat then why do we > still trigger heartbeat request on commit? why not just reset its time on >

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

Hi Ismael, This will solve both binary and source compatibility. Storm has new KafkaSpout that used 0.9.x new KafkaSpout API. As part of that spout we used KafkaConsumer.seekToBeginning and other methods. Since the method

[GitHub] kafka pull request: KAFKA-3617: Unit tests for SASL authenticator

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1273 --- 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] [Updated] (KAFKA-3617) Add unit tests for SASL authentication

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

[jira] [Commented] (KAFKA-3617) Add unit tests for SASL authentication

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

Re: [Release] Status update

Small clarification: "Two KIPs may get in after the release (provided high quality, documented and well-tested PR):" I meant "after the next release candidate but still get into 0.10.0 release" Gwen On Thu, Apr 28, 2016 at 11:02 AM, Ismael Juma wrote: > Thanks for the update

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

Hi Harsha, What is the aim of the PR, is it to fix binary compatibility, source compatibility or both? I think it only fixes source compatibility, so I am interested in what testing has been done to ensure that this fix solves the Storm issue. Thanks, Ismael On Thu, Apr 28, 2016 at 12:58 PM,

Re: No Heartbeat request on commit

I was also wondering that if commitSync acts as heartbeat then why do we still trigger heartbeat request on commit? why not just reset its time on successful commitSync? or am i wrong and we do this already? Regards, Vinay On Thu, Apr 28, 2016 at 3:38 PM, vinay sharma

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

Hi, We missed this vote earlier and realized thats its breaking the 0.9.x client api compatibility. I opened a JIRA here https://issues.apache.org/jira/browse/KAFKA-3633 . Can we keep the old methods with deprecated tag in 0.10 release. Thanks, Harsha On Fri, Mar 18,

Re: [DISCUSSION] KAFKA-3633. Kafka Consumer API breaking backward compatibility

Hi Jason, In my opinion, if one changes the implementation (KafkaConsumer), one is not technically changing the API, which is the Consumer interface. That’s the reason behind coding behind interfaces, that the implementation can change, but the (public) API remains unchanged. We are not

Re: [DISCUSSION] KAFKA-3633. Kafka Consumer API breaking backward compatibility

Hi Jason, Agree and its my bad to not to raise this during the voting of KIP-45. Which I missed it. We can definitely start a vote around it. Thanks, Harsha On Thu, Apr 28, 2016, at 12:45 PM, Jason Gustafson wrote: > Hey Harsha, > > Probably the main concern is that

Re: [DISCUSSION] KAFKA-3633. Kafka Consumer API breaking backward compatibility

Hey Harsha, Probably the main concern is that we already voted to do this in KIP-45. The compatibility concern was brought up in the discussion (I was actually in favor of overloading), but we ultimately decided to make the breaking change to keep the API small. That may or may not have been the

[jira] [Updated] (KAFKA-3636) Increase default group.max.session.timeout.ms to 5 minutes

[ https://issues.apache.org/jira/browse/KAFKA-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3636: --- Summary: Increase default group.max.session.timeout.ms to 5 minutes (was: Increase default

[jira] [Commented] (KAFKA-3636) Increase default group.max.session.timeout.ms to 3 minutes

[ https://issues.apache.org/jira/browse/KAFKA-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262790#comment-15262790 ] Jason Gustafson commented on KAFKA-3636: I talked with [~ijuma] and [~guozhang] and we felt 5

[DISCUSSION] KAFKA-3633. Kafka Consumer API breaking backward compatibility

Hi All, We noticed KIP-45 broke the compatibility with the consumer API that shipped in 0.9.x releases. Hugo posted a patch that only adds these old methods back to KafkaConsumer.java with the deprecated tag. I would like to get this in 0.10 release so that it will help anyone who

[jira] [Commented] (KAFKA-3633) Kafka Consumer API breaking backward compatibility

[ https://issues.apache.org/jira/browse/KAFKA-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262762#comment-15262762 ] Sriharsha Chintalapani commented on KAFKA-3633: --- [~gwenshap] the above patch didn't make any

[jira] [Comment Edited] (KAFKA-3633) Kafka Consumer API breaking backward compatibility

[ https://issues.apache.org/jira/browse/KAFKA-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262756#comment-15262756 ] Gwen Shapira edited comment on KAFKA-3633 at 4/28/16 7:04 PM: -- It doesn't

[jira] [Commented] (KAFKA-3633) Kafka Consumer API breaking backward compatibility

[ https://issues.apache.org/jira/browse/KAFKA-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262756#comment-15262756 ] Gwen Shapira commented on KAFKA-3633: - It doesn't cause immediate issues, but it makes the API more

[jira] [Commented] (KAFKA-3611) Remove WARNs when using reflections

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

[jira] [Updated] (KAFKA-3611) Remove WARNs when using reflections

[ https://issues.apache.org/jira/browse/KAFKA-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3611: - Resolution: Fixed Fix Version/s: (was: 0.10.0.0)

[GitHub] kafka pull request: KAFKA-3611: Remove warnings when using reflect...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1259 --- 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] [Updated] (KAFKA-3637) Add method that checks if streams are initialised

[ https://issues.apache.org/jira/browse/KAFKA-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3637: Assignee: (was: Guozhang Wang) > Add method that checks if streams are initialised >

[jira] [Created] (KAFKA-3637) Add method that checks if streams are initialised

Eno Thereska created KAFKA-3637: --- Summary: Add method that checks if streams are initialised Key: KAFKA-3637 URL: https://issues.apache.org/jira/browse/KAFKA-3637 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-3440) Add Javadoc for KTable (changelog stream) and KStream (record stream)

[ https://issues.apache.org/jira/browse/KAFKA-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3440: --- Description: Currently we only have a 1-liner in {code}KTable{code} and {code}KStream{code}

[jira] [Work started] (KAFKA-3440) Add Javadoc for KTable (changelog stream) and KStream (record stream)

[ https://issues.apache.org/jira/browse/KAFKA-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3440 started by Matthias J. Sax. -- > Add Javadoc for KTable (changelog stream) and KStream (record stream) >

Re: No Heartbeat request on commit

Hi Jason, i reverted back to KAFKA-3149. Producer still had issues related to schema but my consumer worked. Now consumer worked as expected. Although i did not encountered an error and generation was not marked dead by coordinator but i still see that successful heartbeat response are not

[jira] [Resolved] (KAFKA-3574) Add missing @returns tags for JavaDoc

[ https://issues.apache.org/jira/browse/KAFKA-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-3574. Resolution: Duplicate > Add missing @returns tags for JavaDoc >

[jira] [Closed] (KAFKA-3574) Add missing @returns tags for JavaDoc

[ https://issues.apache.org/jira/browse/KAFKA-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax closed KAFKA-3574. -- > Add missing @returns tags for JavaDoc > - > >

[jira] [Updated] (KAFKA-3440) Add Javadoc for KTable (changelog stream) and KStream (record stream)

[ https://issues.apache.org/jira/browse/KAFKA-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3440: --- Description: Currently we only have a 1-liner in {code}KTable{code} and {code}KStream{code}

[jira] [Assigned] (KAFKA-3440) Add Javadoc for KTable (changelog stream) and KStream (record stream)

[ https://issues.apache.org/jira/browse/KAFKA-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-3440: -- Assignee: Matthias J. Sax > Add Javadoc for KTable (changelog stream) and KStream

[jira] [Assigned] (KAFKA-3574) Add missing @returns tags for JavaDoc

[ https://issues.apache.org/jira/browse/KAFKA-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-3574: -- Assignee: Matthias J. Sax (was: Guozhang Wang) > Add missing @returns tags for

[jira] [Updated] (KAFKA-3597) Enable query ConsoleConsumer and VerifiableProducer if they shutdown cleanly

[ https://issues.apache.org/jira/browse/KAFKA-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Povzner updated KAFKA-3597: Status: Patch Available (was: In Progress) > Enable query ConsoleConsumer and VerifiableProducer

[jira] [Commented] (KAFKA-3633) Kafka Consumer API breaking backward compatibility

[ https://issues.apache.org/jira/browse/KAFKA-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262646#comment-15262646 ] Sriharsha Chintalapani commented on KAFKA-3633: --- [~gwenshap] I understand the API is marked

Re: [Release] Status update

Thanks for the update Gwen. Looking at that list, it seems to me that the community did very well in a relatively short period of time (and it doesn't include the large number of bug fixes, test and documentation improvements). Ismael On Thu, Apr 28, 2016 at 10:53 AM, Gwen Shapira

[jira] [Commented] (KAFKA-3294) Kafka REST API

[ https://issues.apache.org/jira/browse/KAFKA-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262631#comment-15262631 ] Sriharsha Chintalapani commented on KAFKA-3294: --- [~lindong] we just shared the initial work

[GitHub] kafka pull request: MINOR: Added more integration tests

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/1285 MINOR: Added more integration tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/enothereska/kafka more-integration-tests Alternatively

[Release] Status update

Hi Team Kafka, Here's a short status update before I am merging trunk into 0.10.0 branch and creating a new release candidate, tomorrow morning. KIPs included in the release: KIP-28 Kafka Streams KIP-31 Relative offsets in compressed messages KIP-32 Add timestamps to messages KIP-36 Rack

[jira] [Commented] (KAFKA-3633) Kafka Consumer API breaking backward compatibility

[ https://issues.apache.org/jira/browse/KAFKA-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262593#comment-15262593 ] Gwen Shapira commented on KAFKA-3633: - I completely understand the pain that this change will cause

[jira] [Commented] (KAFKA-3294) Kafka REST API

[ https://issues.apache.org/jira/browse/KAFKA-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262592#comment-15262592 ] Dong Lin commented on KAFKA-3294: - [~harsha_ch] [~parth.brahmbhatt] This seems to be a big addition to

[GitHub] kafka pull request: KAFKA-3636: change default max session timeout...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1284 KAFKA-3636: change default max session timeout to 3 minutes You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-3636

[jira] [Commented] (KAFKA-3636) Increase default group.max.session.timeout.ms to 3 minutes

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

[jira] [Created] (KAFKA-3636) Increase default group.max.session.timeout.ms to 3 minutes

Jason Gustafson created KAFKA-3636: -- Summary: Increase default group.max.session.timeout.ms to 3 minutes Key: KAFKA-3636 URL: https://issues.apache.org/jira/browse/KAFKA-3636 Project: Kafka

Re: No Heartbeat request on commit

Ah, yeah. That's probably caused by the new topic metadata version, which isn't supported on 0.9 brokers. To test on trunk, you'd have to upgrade the brokers as well. Either that or you can rewind to before KAFKA-3306 (which was just committed the day before yesterday)? -Jason On Thu, Apr 28,

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

Sure thing. Yes, the substantive change is fixing the HC checksum. But to further improve interoperability, the kafka LZ4 class would no longer reject messages that have these optional header flags set. The flags might get set if the client/user chooses to use a non-java lz4 compression library

Re: No Heartbeat request on commit

Hi Jason, I build kafka-client and tried using it but my producers and consumers started throwing below exception. Is 0.10 not going to be compatible with brokers on version 0.9.0.1? or do i need to make some config changes to producers / consumers to make them compatible with brokers on old

[jira] [Updated] (KAFKA-2651) Remove deprecated config alteration from TopicCommand in 0.9.1.0

[ https://issues.apache.org/jira/browse/KAFKA-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-2651: --- Assignee: Manikumar Reddy Status: Patch Available (was: Open) > Remove deprecated

[jira] [Commented] (KAFKA-2651) Remove deprecated config alteration from TopicCommand in 0.9.1.0

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

[GitHub] kafka pull request: KAFKA-2651; Remove deprecated config alteratio...

GitHub user omkreddy opened a pull request: https://github.com/apache/kafka/pull/1283 KAFKA-2651; Remove deprecated config alteration from TopicCommand You can merge this pull request into a Git repository by running: $ git pull https://github.com/omkreddy/kafka KAFKA-2651

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

I'd like to re-initiate the vote for KIP-47 now that KIP-33 has been accepted and is in-progress. I've updated the KIP ( https://cwiki.apache.org/confluence/display/KAFKA/KIP-47+-+Add+timestamp-based+log+deletion+policy). I have a commit with the functionality for KIP-47 ready to go once KIP-33

Re: [VOTE] KIP-50: Move Authorizer to o.a.k.common package - Round 2

Ashish, Thanks for the proposal. +1 Jun On Mon, Apr 25, 2016 at 10:04 AM, Ashish Singh wrote: > Hey Guys, > > I would like to re-initiate the voting process for KIP-50: Move Authorizer > to o.a.k.common package. KIP-50 is available here > < >

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

Hi, Dana, Could you explain the following from the KIP a bit more? The KIP is intended to just fix the HC checksum, but the following seems to suggest there are other format changes? KafkaLZ4* code: - add naive support for optional header flags (ContentSize, ContentChecksum) to enable

[jira] [Assigned] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edoardo Comar reassigned KAFKA-3587: Assignee: Edoardo Comar (was: Manikumar Reddy) > LogCleaner fails due to incorrect offset

[jira] [Updated] (KAFKA-3183) Add metrics for persistent store caching layer

[ https://issues.apache.org/jira/browse/KAFKA-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3183: Assignee: (was: Eno Thereska) > Add metrics for persistent store caching layer >

[jira] [Updated] (KAFKA-3598) Improve JavaDoc of public API

[ https://issues.apache.org/jira/browse/KAFKA-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3598: --- Status: Patch Available (was: In Progress) > Improve JavaDoc of public API >

[jira] [Created] (KAFKA-3635) Broker leadership state can become inconsistent between Zookeeper/MetadataCache and the ReplicaManager's Partition

Stig Rohde Døssing created KAFKA-3635: - Summary: Broker leadership state can become inconsistent between Zookeeper/MetadataCache and the ReplicaManager's Partition Key: KAFKA-3635 URL:

[jira] [Created] (KAFKA-3634) Add ducktape tests for upgrade with SASL

Rajini Sivaram created KAFKA-3634: - Summary: Add ducktape tests for upgrade with SASL Key: KAFKA-3634 URL: https://issues.apache.org/jira/browse/KAFKA-3634 Project: Kafka Issue Type: Test

[jira] [Updated] (KAFKA-2693) Run relevant ducktape tests with SASL/PLAIN and multiple mechanisms

[ https://issues.apache.org/jira/browse/KAFKA-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-2693: -- Status: Patch Available (was: Open) > Run relevant ducktape tests with SASL/PLAIN and multiple

  1   2   >