[jira] [Resolved] (KAFKA-3276) Rename 0.10.0.0 to 0.10.1.0 and 0.9.1.0 to 0.10.0.0 in JIRA

[ https://issues.apache.org/jira/browse/KAFKA-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3276. -- Resolution: Fixed Assignee: Ewen Cheslack-Postava Reviewer:

[jira] [Updated] (KAFKA-3276) Rename 0.10.0.0 to 0.10.1.0 and 0.9.1.0 to 0.10.0.0 in JIRA

[ https://issues.apache.org/jira/browse/KAFKA-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3276: - Fix Version/s: 0.10.1.0 > Rename 0.10.0.0 to 0.10.1.0 and 0.9.1.0 to 0.10.0.0 in

[jira] [Updated] (KAFKA-3036) Add up-conversion and down-conversion of ProducerRequest and FetchRequest to broker.

[ https://issues.apache.org/jira/browse/KAFKA-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3036: --- Fix Version/s: (was: 0.10.0.0) 0.9.1.0 > Add up-conversion and down-conversion

[jira] [Commented] (KAFKA-3026) KIP-32 (part 2): Changes in broker to over-write timestamp or reject message

[ https://issues.apache.org/jira/browse/KAFKA-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15160283#comment-15160283 ] Ismael Juma commented on KAFKA-3026: Thanks, that's what I thought. > KIP-32 (part 2): Changes in

[jira] [Updated] (KAFKA-3026) KIP-32 (part 2): Changes in broker to over-write timestamp or reject message

[ https://issues.apache.org/jira/browse/KAFKA-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3026: --- Fix Version/s: (was: 0.10.0.0) 0.9.1.0 > KIP-32 (part 2): Changes in broker to

[jira] [Commented] (KAFKA-3093) Keep track of connector and task status info, expose it via the REST API

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

[jira] [Commented] (KAFKA-3036) Add up-conversion and down-conversion of ProducerRequest and FetchRequest to broker.

[ https://issues.apache.org/jira/browse/KAFKA-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15160276#comment-15160276 ] Jiangjie Qin commented on KAFKA-3036: - Yes. I'll close it. > Add up-conversion and down-conversion of

[jira] [Resolved] (KAFKA-3036) Add up-conversion and down-conversion of ProducerRequest and FetchRequest to broker.

[ https://issues.apache.org/jira/browse/KAFKA-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-3036. - Resolution: Fixed Fix Version/s: (was: 0.9.1.0) 0.10.0.0 This

[GitHub] kafka pull request: KAFKA-3093: Add Connect status tracking API

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/920 --- 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] [Resolved] (KAFKA-3093) Keep track of connector and task status info, expose it via the REST API

[ https://issues.apache.org/jira/browse/KAFKA-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3093. -- Resolution: Fixed Fix Version/s: 0.9.1.0 Issue resolved by pull request

[jira] [Resolved] (KAFKA-3026) KIP-32 (part 2): Changes in broker to over-write timestamp or reject message

[ https://issues.apache.org/jira/browse/KAFKA-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-3026. - Resolution: Fixed Fix Version/s: 0.10.0.0 This ticket has been implemented in KAFKA-3025

[jira] [Commented] (KAFKA-3026) KIP-32 (part 2): Changes in broker to over-write timestamp or reject message

[ https://issues.apache.org/jira/browse/KAFKA-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15160274#comment-15160274 ] Jiangjie Qin commented on KAFKA-3026: - This has actually been down. We used one ticket to finish the

Re: [VOTE] Make next Kafka release 0.10.0.0 instead of 0.9.1.0

I also changed the "Fix version" for a number of recent JIRAs from 0.10.0.0 to 0.9.1.0. The reason is that once we rename the JIRA versions (as per KAFKA-3276), they will all automatically become 0.10.0.0 (without causing a storm of notifications). Ismael On Tue, Feb 23, 2016 at 10:26 PM, Ismael

[jira] [Updated] (KAFKA-1377) transient unit test failure in LogOffsetTest

[ https://issues.apache.org/jira/browse/KAFKA-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1377: --- Fix Version/s: (was: 0.10.0.0) 0.9.1.0 > transient unit test failure in

[jira] [Updated] (KAFKA-2511) KIP-31 & KIP-32: message format change + adding timestamp to messages

[ https://issues.apache.org/jira/browse/KAFKA-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2511: --- Fix Version/s: (was: 0.10.0.0) 0.9.1.0 > KIP-31 & KIP-32: message format

[jira] [Commented] (KAFKA-3026) KIP-32 (part 2): Changes in broker to over-write timestamp or reject message

[ https://issues.apache.org/jira/browse/KAFKA-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15160262#comment-15160262 ] Ismael Juma commented on KAFKA-3026: [~becket_qin], what's the status of this? > KIP-32 (part 2):

[jira] [Updated] (KAFKA-1332) Add functionality to the offsetsBeforeTime() API

[ https://issues.apache.org/jira/browse/KAFKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1332: --- Fix Version/s: 0.9.1.0 > Add functionality to the offsetsBeforeTime() API >

[jira] [Updated] (KAFKA-3036) Add up-conversion and down-conversion of ProducerRequest and FetchRequest to broker.

[ https://issues.apache.org/jira/browse/KAFKA-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3036: --- Fix Version/s: (was: 0.10.0.0) 0.9.1.0 > Add up-conversion and down-conversion

[jira] [Updated] (KAFKA-1332) Add functionality to the offsetsBeforeTime() API

[ https://issues.apache.org/jira/browse/KAFKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1332: --- Affects Version/s: (was: 0.10.0.0) 0.9.0.0 > Add functionality to the

[jira] [Updated] (KAFKA-1332) Add functionality to the offsetsBeforeTime() API

[ https://issues.apache.org/jira/browse/KAFKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1332: --- Fix Version/s: (was: 0.10.0.0) > Add functionality to the offsetsBeforeTime() API >

[jira] [Updated] (KAFKA-3101) Optimize Aggregation Outputs

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

[jira] [Updated] (KAFKA-1545) java.net.InetAddress.getLocalHost in KafkaHealthcheck.register may fail on some irregular hostnames

[ https://issues.apache.org/jira/browse/KAFKA-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1545: --- Fix Version/s: (was: 0.10.0.0) > java.net.InetAddress.getLocalHost in KafkaHealthcheck.register

[jira] [Commented] (KAFKA-3036) Add up-conversion and down-conversion of ProducerRequest and FetchRequest to broker.

[ https://issues.apache.org/jira/browse/KAFKA-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15160257#comment-15160257 ] Ismael Juma commented on KAFKA-3036: [~becket_qin], this has been done right? > Add up-conversion and

[jira] [Updated] (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 ] Ismael Juma updated KAFKA-3202: --- Fix Version/s: (was: 0.10.0.0) 0.9.1.0 > Add system test for KIP-31 and KIP-32

[jira] [Updated] (KAFKA-3163) KIP-33 - Add a time based log index to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3163: --- Fix Version/s: (was: 0.10.0.0) 0.9.1.0 > KIP-33 - Add a time based log index

[jira] [Updated] (KAFKA-2522) ConsumerGroupCommand sends all output to STDOUT

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

[jira] [Updated] (KAFKA-3188) Add system test for KIP-31 and KIP-32 - Compatibility Test

[ https://issues.apache.org/jira/browse/KAFKA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3188: --- Fix Version/s: (was: 0.10.0.0) 0.9.1.0 > Add system test for KIP-31 and KIP-32

[jira] [Updated] (KAFKA-1215) Rack-Aware replica assignment option

[ https://issues.apache.org/jira/browse/KAFKA-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1215: --- Fix Version/s: (was: 0.10.0.0) 0.9.1.0 > Rack-Aware replica assignment option

[jira] [Updated] (KAFKA-3257) bootstrap-test-env.sh version check fails when grep has --colour option enabled.

[ https://issues.apache.org/jira/browse/KAFKA-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3257: --- Fix Version/s: (was: 0.10.0.0) 0.9.1.0 > bootstrap-test-env.sh version check

[jira] [Updated] (KAFKA-3046) add ByteBuffer Serializer

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

[jira] [Updated] (KAFKA-3245) need a way to specify the number of replicas for change log topics

[ https://issues.apache.org/jira/browse/KAFKA-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3245: --- Fix Version/s: (was: 0.10.0.0) 0.9.1.0 > need a way to specify the number of

[jira] [Updated] (KAFKA-3201) Add system test for KIP-31 and KIP-32 - Upgrade Test

[ https://issues.apache.org/jira/browse/KAFKA-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3201: --- Fix Version/s: (was: 0.10.0.0) 0.9.1.0 > Add system test for KIP-31 and KIP-32

[jira] [Updated] (KAFKA-3253) Skip duplicate message size check if there is no re-compression during log appending.

[ https://issues.apache.org/jira/browse/KAFKA-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3253: --- Fix Version/s: (was: 0.10.0.0) 0.9.1.0 > Skip duplicate message size check if

[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 ] Ismael Juma updated KAFKA-2982: --- Fix Version/s: (was: 0.10.0.0) 0.9.1.0 > Mark the old Scala producer and

Re: [VOTE] Make next Kafka release 0.10.0.0 instead of 0.9.1.0

Thank you Becket. I have: * Updated KIP wiki page so that all KIPs with a target of 0.9.1.0 now target 0.10.0.0 * Filed https://issues.apache.org/jira/browse/KAFKA-3275 to track tasks that still need to be done. The next step would be to update JIRA versions as per

[jira] [Updated] (KAFKA-3277) Update trunk version to be 0.10.0.0-SNAPSHOT

[ https://issues.apache.org/jira/browse/KAFKA-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3277: --- Status: Patch Available (was: Open) > Update trunk version to be 0.10.0.0-SNAPSHOT >

[jira] [Commented] (KAFKA-3277) Update trunk version to be 0.10.0.0-SNAPSHOT

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

[GitHub] kafka pull request: KAFKA-3277; Update trunk version to be 0.10.0....

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/963 KAFKA-3277; Update trunk version to be 0.10.0.0-SNAPSHOT Also update `kafka-merge-pr.py` and `tests/kafkatest/__init__.py`. You can merge this pull request into a Git repository by running: $ git

[jira] [Created] (KAFKA-3277) Update trunk version to be 0.10.0.0-SNAPSHOT

Ismael Juma created KAFKA-3277: -- Summary: Update trunk version to be 0.10.0.0-SNAPSHOT Key: KAFKA-3277 URL: https://issues.apache.org/jira/browse/KAFKA-3277 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-3276) Rename 0.10.0.0 to 0.10.1.0 and 0.9.1.0 to 0.10.0.0 in JIRA

Ismael Juma created KAFKA-3276: -- Summary: Rename 0.10.0.0 to 0.10.1.0 and 0.9.1.0 to 0.10.0.0 in JIRA Key: KAFKA-3276 URL: https://issues.apache.org/jira/browse/KAFKA-3276 Project: Kafka Issue

[jira] [Created] (KAFKA-3275) Replace 0.9.1.0 references with 0.10.0.0

Ismael Juma created KAFKA-3275: -- Summary: Replace 0.9.1.0 references with 0.10.0.0 Key: KAFKA-3275 URL: https://issues.apache.org/jira/browse/KAFKA-3275 Project: Kafka Issue Type: Task

[jira] [Updated] (KAFKA-1196) java.lang.IllegalArgumentException Buffer.limit on FetchResponse.scala + 33

[ https://issues.apache.org/jira/browse/KAFKA-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1196: --- Priority: Critical (was: Blocker) > java.lang.IllegalArgumentException Buffer.limit on

[jira] [Commented] (KAFKA-1196) java.lang.IllegalArgumentException Buffer.limit on FetchResponse.scala + 33

[ https://issues.apache.org/jira/browse/KAFKA-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15160213#comment-15160213 ] Ewen Cheslack-Postava commented on KAFKA-1196: -- [~ijuma] Pretty sure I didn't set the fix

[jira] [Commented] (KAFKA-1196) java.lang.IllegalArgumentException Buffer.limit on FetchResponse.scala + 33

[ https://issues.apache.org/jira/browse/KAFKA-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15160205#comment-15160205 ] Ismael Juma commented on KAFKA-1196: [~ewencp], this is marked as "Blocker" with a "Fix Version" of

Re: new producer failed with org.apache.kafka.common.errors.TimeoutException

Kris, This is a bit surprising, but handling the bootstrap servers, broker failures/retirement, and cluster metadata properly is surprisingly hard to get right! https://issues.apache.org/jira/browse/KAFKA-1843 explains some of the challenges. https://issues.apache.org/jira/browse/KAFKA-3068

[jira] [Commented] (KAFKA-3274) Document command line tools

[ https://issues.apache.org/jira/browse/KAFKA-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15160150#comment-15160150 ] Gwen Shapira commented on KAFKA-3274: - Docs collocated with source. Since they are properly versioned.

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

See

add karma to jira

can someone add karma to my username 'ceposta' to be able to assign jira's to myself? thanks! -- *Christian Posta* twitter: @christianposta http://www.christianposta.com/blog http://fabric8.io

[jira] [Commented] (KAFKA-2698) add paused API

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

[GitHub] kafka pull request: KAFKA-2698: Add paused() method to o.a.k.c.c.C...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/962 KAFKA-2698: Add paused() method to o.a.k.c.c.Consumer You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-2698

[jira] [Commented] (KAFKA-1382) Update zkVersion on partition state update failures

[ https://issues.apache.org/jira/browse/KAFKA-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15160030#comment-15160030 ] dude commented on KAFKA-1382: - we hit this when there is a network problem, which the kakfa broker 3 can not

[GitHub] kafka pull request: KAFKA-3018: added topic name validator to Prod...

GitHub user choang opened a pull request: https://github.com/apache/kafka/pull/961 KAFKA-3018: added topic name validator to ProducerRecord Added validation for topic name when creating a `ProducerRecord`, and added corresponding tests. You can merge this pull request into a Git

[jira] [Commented] (KAFKA-3018) Kafka producer hangs on producer.close() call if the producer topic contains single quotes in the topic name

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

[jira] [Commented] (KAFKA-3201) Add system test for KIP-31 and KIP-32 - Upgrade Test

[ https://issues.apache.org/jira/browse/KAFKA-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15160007#comment-15160007 ] Jiangjie Qin commented on KAFKA-3201: - [~apovzner] Yes, that was what I had in mind. Thanks for

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

See Changes: [wangguoz] KAFKA-3245: config for changelog replication factor [wangguoz] HOTFIX: fix consumer config for streams [wangguoz] KAFKA-3046: Add ByteBuffer Serializer and Deserializer [cshapi] MINOR: KTable.count() to only

Re: [VOTE] Make next Kafka release 0.10.0.0 instead of 0.9.1.0

Thanks everyone for voting. The vote has passed with +6 (binding) and +5(non-binding) Jiangjie (Becket) Qin On Tue, Feb 23, 2016 at 2:38 PM, Harsha wrote: > +1 > > On Tue, Feb 23, 2016, at 02:25 PM, Christian Posta wrote: > > +1 non binding > > > > On Tue, Feb 23, 2016 at

Re: [VOTE] KIP-33 - Add a time based log index to Kafka

Bump. Per Jun's comments during KIP hangout, I have updated wiki with the upgrade plan or KIP-33. Let's vote! Thanks, Jiangjie (Becket) Qin On Wed, Feb 3, 2016 at 10:32 AM, Becket Qin wrote: > Hi all, > > I would like to initiate the vote for KIP-33. > >

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

See Changes: [wangguoz] KAFKA-3245: config for changelog replication factor [wangguoz] HOTFIX: fix consumer config for streams [wangguoz] KAFKA-3046: Add ByteBuffer Serializer and Deserializer [cshapi] MINOR: KTable.count() to only

[jira] [Commented] (KAFKA-3274) Document command line tools

[ https://issues.apache.org/jira/browse/KAFKA-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159966#comment-15159966 ] Christian Posta commented on KAFKA-3274: Where's the best place to put this? In the docs

[jira] [Created] (KAFKA-3274) Document command line tools

Gwen Shapira created KAFKA-3274: --- Summary: Document command line tools Key: KAFKA-3274 URL: https://issues.apache.org/jira/browse/KAFKA-3274 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-3273) MessageFormatter and MessageReader interfaces should be resilient to changes

[ https://issues.apache.org/jira/browse/KAFKA-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159906#comment-15159906 ] Ismael Juma commented on KAFKA-3273: Thanks for clarifying [~ewencp]. > MessageFormatter and

[jira] [Commented] (KAFKA-3272) Add debugging options to kafka-run-class.sh so we can easily run remote debugging

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

[jira] [Resolved] (KAFKA-3272) Add debugging options to kafka-run-class.sh so we can easily run remote debugging

[ https://issues.apache.org/jira/browse/KAFKA-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-3272. - Resolution: Fixed Fix Version/s: 0.9.1.0 Issue resolved by pull request 955

[GitHub] kafka pull request: KAFKA-3272: Add debugging options to kafka-run...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/955 --- 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-3273) MessageFormatter and MessageReader interfaces should be resilient to changes

[ https://issues.apache.org/jira/browse/KAFKA-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159899#comment-15159899 ] Ewen Cheslack-Postava commented on KAFKA-3273: -- To clarify my thoughts, I don't think these

[jira] [Created] (KAFKA-3273) MessageFormatter and MessageReader interfaces should be resilient to changes

Ismael Juma created KAFKA-3273: -- Summary: MessageFormatter and MessageReader interfaces should be resilient to changes Key: KAFKA-3273 URL: https://issues.apache.org/jira/browse/KAFKA-3273 Project:

[jira] [Updated] (KAFKA-3273) MessageFormatter and MessageReader interfaces should be resilient to changes

[ https://issues.apache.org/jira/browse/KAFKA-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3273: --- Description: They should use `ConsumerRecord` and `ProducerRecord` as parameters and return types

[jira] [Resolved] (KAFKA-3007) Implement max.poll.records for new consumer (KIP-41)

[ https://issues.apache.org/jira/browse/KAFKA-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3007. -- Resolution: Fixed Fix Version/s: 0.9.1.0 Issue resolved by pull request

[GitHub] kafka pull request: KAFKA-3007: implement max.poll.records (KIP-41...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/931 --- 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-3007) Implement max.poll.records for new consumer (KIP-41)

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

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

Great - thanks for clarifying. Joel On Tue, Feb 23, 2016 at 1:47 PM, Bill Warshaw wrote: > Sorry that I didn't see this comment before the meeting Joel. I'll try to > clarify what I said at the meeting: > > - The KIP currently states that timestamp-based log deletion will

[GitHub] kafka pull request: HOTFIX: Add missing file for KeyValue unit tes...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/960 --- 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: [DISCUSS] Deprecating the old Scala producers for the next release

Hi Andrew, Thanks for your input. On Tue, Feb 23, 2016 at 11:16 AM, Andrew Schofield < andrew_schofield_j...@outlook.com> wrote: > From my point of view, it seems very odd to deprecate the Scala producer > but not the consumer. So, I would vote to deprecate them both in 0.10. > I explained in

[GitHub] kafka pull request: HOTFIX: Add missing file for KeyValue unit tes...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/960 HOTFIX: Add missing file for KeyValue unit test You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka KCountP1 Alternatively

[GitHub] kafka pull request: MINOR: KTable.count() to only take a selector ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/872 --- 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-3046) add ByteBuffer Serializer

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

[jira] [Resolved] (KAFKA-3046) add ByteBuffer Serializer

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

[GitHub] kafka pull request: KAFKA-3046: add ByteBuffer Serializer.

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/718 --- 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: [DISCUSS] Deprecating the old Scala producers for the next release

Hi Flavio, On Tue, Feb 23, 2016 at 10:46 AM, Flavio Junqueira wrote: > It does make sense, thanks for the clarification. If we deprecate the > producer first, does it mean that the following release won't have a scala > producer but will have a scala consumer? Actually I should

Re: [DISCUSS] Deprecating the old Scala producers for the next release

Hi Jay, Comments inline. On Tue, Feb 23, 2016 at 10:38 AM, Jay Kreps wrote: > Would it make more sense to be able to announce both new clients stable and > deprecate both the scala clients at the same time (irrespective of whether > that is next release or one after)? I

[jira] [Updated] (KAFKA-3245) need a way to specify the number of replicas for change log topics

[ https://issues.apache.org/jira/browse/KAFKA-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3245: - Assignee: Yasuhiro Matsuda > need a way to specify the number of replicas for change log topics >

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

See Changes: [cshapi] KAFKA-3242: minor rename / logging change to Controller -- [...truncated 2972 lines...] kafka.log.LogTest > testTimeBasedLogRoll PASSED kafka.log.LogTest >

[jira] [Resolved] (KAFKA-3245) need a way to specify the number of replicas for change log topics

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

[GitHub] kafka pull request: HOTFIX: fix consumer config for streams

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/959 --- 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-3245) need a way to specify the number of replicas for change log topics

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

[GitHub] kafka pull request: KAFKA-3245: config for changelog replication f...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/948 --- 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-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=15159808#comment-15159808 ] ASF GitHub Bot commented on KAFKA-2832: --- Github user vahidhashemian closed the pull request at:

[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=15159809#comment-15159809 ] ASF GitHub Bot commented on KAFKA-2832: --- GitHub user vahidhashemian reopened a pull request:

[GitHub] kafka pull request: HOTFIX: fix consumer config for streams

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/959 HOTFIX: fix consumer config for streams @guozhangwang My bad. I removed ZOOKEEPER_CONNECT_CONFIG from consumer's config by mistake. It is needed by our own partition assigner running in

[GitHub] kafka pull request: KAFKA-2832: Add a consumer config option to ex...

GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/932 KAFKA-2832: Add a consumer config option to exclude internal topics A new consumer config option 'exclude.internal.topics' was added to allow excluding internal topics when wildcards are

[GitHub] kafka pull request: KAFKA-2832: Add a consumer config option to ex...

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

Re: [VOTE] Make next Kafka release 0.10.0.0 instead of 0.9.1.0

+1 On Tue, Feb 23, 2016, at 02:25 PM, Christian Posta wrote: > +1 non binding > > On Tue, Feb 23, 2016 at 3:18 PM, Gwen Shapira wrote: > > > +1 > > > > On Tue, Feb 23, 2016 at 1:58 PM, Jun Rao wrote: > > > > > +1. > > > > > > Thanks, > > > > > > Jun > > >

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

See

[jira] [Commented] (KAFKA-3214) Add consumer system tests for compressed topics

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

[GitHub] kafka pull request: KAFKA-3214: Added system tests for compressed ...

GitHub user apovzner opened a pull request: https://github.com/apache/kafka/pull/958 KAFKA-3214: Added system tests for compressed topics Added the following tests: 1. Extended TestVerifiableProducer (sanity check test) to test Trunk with snappy compression (one producer/one

Re: [VOTE] Make next Kafka release 0.10.0.0 instead of 0.9.1.0

+1 non binding On Tue, Feb 23, 2016 at 3:18 PM, Gwen Shapira wrote: > +1 > > On Tue, Feb 23, 2016 at 1:58 PM, Jun Rao wrote: > > > +1. > > > > Thanks, > > > > Jun > > > > On Fri, Feb 19, 2016 at 11:00 AM, Becket Qin > wrote: > > > >

Re: [VOTE] Make next Kafka release 0.10.0.0 instead of 0.9.1.0

+1 On Tue, Feb 23, 2016 at 1:58 PM, Jun Rao wrote: > +1. > > Thanks, > > Jun > > On Fri, Feb 19, 2016 at 11:00 AM, Becket Qin wrote: > > > Hi All, > > > > We would like to start this voting thread on making next Kafka release > > 0.10.0.0 instead of

[GitHub] kafka pull request: Minor: add useful debug log messages to KConne...

GitHub user gwenshap opened a pull request: https://github.com/apache/kafka/pull/957 Minor: add useful debug log messages to KConnect source task execution You can merge this pull request into a Git repository by running: $ git pull https://github.com/gwenshap/kafka

[jira] [Commented] (KAFKA-3271) Notification upon unclean leader election

[ https://issues.apache.org/jira/browse/KAFKA-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159732#comment-15159732 ] Monal Daxini commented on KAFKA-3271: - If there is an api to query a broker (leader of a partition)

Re: [VOTE] Make next Kafka release 0.10.0.0 instead of 0.9.1.0

+1. Thanks, Jun On Fri, Feb 19, 2016 at 11:00 AM, Becket Qin wrote: > Hi All, > > We would like to start this voting thread on making next Kafka release > 0.10.0.0 instead of 0.9.1.0. > > The next Kafka release will have several significant important new >

  1   2   >