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

See Changes: [wangguoz] MINOR: catch a commit failure due to rebalance in StreamThread -- [...truncated 1486 lines...] kafka.log.LogTest > testTruncateTo PASSED kafka.log.LogTest >

[jira] [Commented] (KAFKA-3263) Add Markdown support for ConfigDef

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

[GitHub] kafka pull request: KAFKA-3263 - Support for markdown generation.

GitHub user jcustenborder opened a pull request: https://github.com/apache/kafka/pull/952 KAFKA-3263 - Support for markdown generation. Added support to generate markdown from ConfigDef entries. Added test toMarkdown() to ConfigDefTest. Added toMarkdown() to ConfigDef. You can

[jira] [Created] (KAFKA-3263) Add Markdown support for ConfigDef

Jeremy Custenborder created KAFKA-3263: -- Summary: Add Markdown support for ConfigDef Key: KAFKA-3263 URL: https://issues.apache.org/jira/browse/KAFKA-3263 Project: Kafka Issue Type:

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

+1 It will be great If we can completely close below issue. https://issues.apache.org/jira/browse/KAFKA-1843 On Tue, Feb 23, 2016 at 3:25 AM, Joel Koshy wrote: > +1 > > Thanks for bringing it up > > On Mon, Feb 22, 2016 at 9:36 AM, Ismael Juma wrote:

[GitHub] kafka pull request: MINOR: catch a commit failure due to rebalance

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

[GitHub] kafka pull request: HOTFIX: check offset limits in streamtask when...

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

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

Hi All, I saw an issue today wherein the producers (new producers) started to fail with org.apache.kafka.common.errors.TimeoutException: Failed to update metadata after 6 ms. This issue happened when we took down one of the 6 brokers (running version 0.8.2.1) for planned maintenance

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

See Changes: [jjkoshy] MINOR - remove unused imports in package kafka.utils -- [...truncated 1474 lines...] kafka.log.LogTest > testTruncateTo PASSED kafka.log.LogTest > testCleanShutdownFile

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

See Changes: [jjkoshy] MINOR - remove unused imports in package kafka.utils -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-us1 (Ubuntu

[GitHub] kafka pull request: MINOR - remove unused imports in package kafka...

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

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

See Changes: [junrao] KAFKA-3256; Add print.timestamp option to console consumer. -- [...truncated 5633 lines...] org.apache.kafka.connect.runtime.WorkerTest > testStopInvalidTask PASSED

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

See

[jira] [Updated] (KAFKA-3262) Make KafkaStreams debugging friendly

[ https://issues.apache.org/jira/browse/KAFKA-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yasuhiro Matsuda updated KAFKA-3262: Description: Current KafkaStreams polls records in the same thread as the data processing

[jira] [Created] (KAFKA-3262) Make KafkaStreams debugging friendly

Yasuhiro Matsuda created KAFKA-3262: --- Summary: Make KafkaStreams debugging friendly Key: KAFKA-3262 URL: https://issues.apache.org/jira/browse/KAFKA-3262 Project: Kafka Issue Type:

[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=15158019#comment-15158019 ] Chi Hoang commented on KAFKA-3018: -- I encountered this, if not a similar, problem. I unknowingly had

[jira] [Work started] (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 ] Work on KAFKA-3201 started by Anna Povzner. --- > Add system test for KIP-31 and KIP-32 - Upgrade Test >

[jira] [Commented] (KAFKA-3261) Consolidate class kafka.cluster.BrokerEndPoint and kafka.cluster.EndPoint

[ https://issues.apache.org/jira/browse/KAFKA-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157976#comment-15157976 ] chen zhu commented on KAFKA-3261: - [~guozhang] Thanks for creating the patch. I will finish this one as

[jira] [Issue Comment Deleted] (KAFKA-3261) Consolidate class kafka.cluster.BrokerEndPoint and kafka.cluster.EndPoint

[ https://issues.apache.org/jira/browse/KAFKA-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chen zhu updated KAFKA-3261: Comment: was deleted (was: @guozhang Thanks for creating the patch. I will finish this one as follow-up

[jira] [Commented] (KAFKA-3261) Consolidate class kafka.cluster.BrokerEndPoint and kafka.cluster.EndPoint

[ https://issues.apache.org/jira/browse/KAFKA-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157974#comment-15157974 ] chen zhu commented on KAFKA-3261: - @guozhang Thanks for creating the patch. I will finish this one as

[jira] [Assigned] (KAFKA-3261) Consolidate class kafka.cluster.BrokerEndPoint and kafka.cluster.EndPoint

[ https://issues.apache.org/jira/browse/KAFKA-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chen zhu reassigned KAFKA-3261: --- Assignee: chen zhu > Consolidate class kafka.cluster.BrokerEndPoint and kafka.cluster.EndPoint >

[jira] [Commented] (KAFKA-3256) Large number of system test failures

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

[GitHub] kafka pull request: KAFKA-3256: Add print.timestamp option to cons...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/949 --- 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-3256) Large number of system test failures

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

[jira] [Commented] (KAFKA-3196) KIP-42 (part 2): add record size and CRC to RecordMetadata and ConsumerRecords

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

[GitHub] kafka pull request: KAFKA-3196: Added checksum and size to RecordM...

GitHub user apovzner opened a pull request: https://github.com/apache/kafka/pull/951 KAFKA-3196: Added checksum and size to RecordMetadata and ConsumerRecordetadata and ConsumerRecord This is the second (remaining) part of KIP-42. See

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

See Changes: [wangguoz] MINOR: Update streams RocksDb to 4.1.0 [wangguoz] HOTFIX: make sure to go through all shutdown steps -- [...truncated 2394 lines...]

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

Sounds good. I'll hold off on sending out a VOTE thread until after the KIP meeting tomorrow. On Mon, Feb 22, 2016 at 12:56 PM, Becket Qin wrote: > Hi Jun, > > I think it makes sense to implement KIP-47 after KIP-33 so we can make it > work for both LogAppendTime and

[jira] [Commented] (KAFKA-3260) Increase the granularity of commit for SourceTask

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

[GitHub] kafka pull request: KAFKA-3260 - Added SourceTask.commitRecord

GitHub user jcustenborder opened a pull request: https://github.com/apache/kafka/pull/950 KAFKA-3260 - Added SourceTask.commitRecord Added commitRecord(SourceRecord record) to SourceTask. This method is called during the callback from producer.send() when the message has been sent

Re: Kafka KIP meeting Feb 23 at 11:00am PST

Jun, Could we also discuss *KIP-43: Kafka SASL enhancements* in the meeting tomorrow? Thank you. On Mon, Feb 22, 2016 at 10:16 PM, Jun Rao wrote: > Hi, Everyone, > > We will have a Kafka KIP meeting tomorrow at 11:00am PST. If you plan to > attend but haven't received an

[jira] [Commented] (KAFKA-2970) Both UpdateMetadataRequest.java and LeaderAndIsrRequest.java have an Endpoint class

[ https://issues.apache.org/jira/browse/KAFKA-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157821#comment-15157821 ] Ismael Juma commented on KAFKA-2970: >From a protocol perspective, it's probably OK to go that way.

Kafka KIP meeting Feb 23 at 11:00am PST

Hi, Everyone, We will have a Kafka KIP meeting tomorrow at 11:00am PST. If you plan to attend but haven't received an invite, please let me know. The following is the agenda. Agenda: KIP-33 - Add a time based log index to Kafka KIP-47 - Add timestamp-based log deletion policy Thanks, Jun

[jira] [Updated] (KAFKA-3261) Consolidate class kafka.cluster.BrokerEndPoint and kafka.cluster.EndPoint

[ https://issues.apache.org/jira/browse/KAFKA-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3261: - Description: These two classes are serving similar purposes and can be consolidated. Also as

[jira] [Created] (KAFKA-3261) Consolidate class kafka.cluster.BrokerEndPoint and kafka.cluster.EndPoint

Guozhang Wang created KAFKA-3261: Summary: Consolidate class kafka.cluster.BrokerEndPoint and kafka.cluster.EndPoint Key: KAFKA-3261 URL: https://issues.apache.org/jira/browse/KAFKA-3261 Project:

[jira] [Commented] (KAFKA-3256) Large number of system test failures

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

[jira] [Updated] (KAFKA-3256) Large number of system test failures

[ https://issues.apache.org/jira/browse/KAFKA-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3256: Status: Patch Available (was: Open) > Large number of system test failures >

[GitHub] kafka pull request: KAFKA-3256: Add print.timestamp option to cons...

GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/949 KAFKA-3256: Add print.timestamp option to console consumer. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3256

[jira] [Assigned] (KAFKA-3248) AdminClient Blocks Forever in send Method

[ https://issues.apache.org/jira/browse/KAFKA-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Warren Green reassigned KAFKA-3248: --- Assignee: Warren Green > AdminClient Blocks Forever in send Method >

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

See Changes: [wangguoz] MINOR: Update streams RocksDb to 4.1.0 [wangguoz] HOTFIX: make sure to go through all shutdown steps -- Started by an SCM change [EnvInject] - Loading node environment

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

+1 Thanks for bringing it up On Mon, Feb 22, 2016 at 9:36 AM, Ismael Juma wrote: > Hi all, > > The new Java producer was introduced in 0.8.2.0 (released in February > 2015). It has become the default implementation for various tools since > 0.9.0.0 (released in October 2015)

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

See Changes: [cshapi] MINOR: Example style improvements -- [...truncated 5012 lines...] org.apache.kafka.streams.state.internals.InMemoryLRUCacheStoreTest > testPutGetRangeWithDefaultSerdes

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

See Changes: [cshapi] MINOR: Example style improvements -- [...truncated 1479 lines...] kafka.log.LogTest > testTruncateTo PASSED kafka.log.LogTest > testCleanShutdownFile PASSED

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

+1 On Mon, Feb 22, 2016 at 1:25 PM, Guozhang Wang wrote: > +1. I feel it is the right time to do so in 0.10.0.0. > > On Tue, Feb 23, 2016 at 1:58 AM, Becket Qin wrote: > > > +1 on deprecating old producer. > > > > On Mon, Feb 22, 2016 at 9:36 AM,

[jira] [Commented] (KAFKA-2970) Both UpdateMetadataRequest.java and LeaderAndIsrRequest.java have an Endpoint class

[ https://issues.apache.org/jira/browse/KAFKA-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157728#comment-15157728 ] Guozhang Wang commented on KAFKA-2970: -- I merged in the patch of KAFKA-2757 which actually get rid of

[jira] [Commented] (KAFKA-2214) kafka-reassign-partitions.sh --verify should return non-zero exit codes when reassignment is not completed yet

[ https://issues.apache.org/jira/browse/KAFKA-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157726#comment-15157726 ] Jack Lund commented on KAFKA-2214: -- Has any progress been made on this, or has it been rejected? We also

[jira] [Commented] (KAFKA-3256) Large number of system test failures

[ https://issues.apache.org/jira/browse/KAFKA-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157723#comment-15157723 ] Anna Povzner commented on KAFKA-3256: - [~becket_qin] I wrote my comment without seeing yours. Yes, I

[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=15157720#comment-15157720 ] ASF GitHub Bot commented on KAFKA-3245: --- GitHub user ymatsuda opened a pull request:

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

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/948 KAFKA-3245: config for changelog replication factor @guozhangwang You can merge this pull request into a Git repository by running: $ git pull https://github.com/ymatsuda/kafka

[jira] [Commented] (KAFKA-3256) Large number of system test failures

[ https://issues.apache.org/jira/browse/KAFKA-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157719#comment-15157719 ] Anna Povzner commented on KAFKA-3256: - FYI: The upgrade test fails with this error:

[GitHub] kafka pull request: HOTFIX: check offset limits in streamtask when...

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/947 HOTFIX: check offset limits in streamtask when recovering KTable store @guozhangwang You can merge this pull request into a Git repository by running: $ git pull

[jira] [Comment Edited] (KAFKA-3256) Large number of system test failures

[ https://issues.apache.org/jira/browse/KAFKA-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157715#comment-15157715 ] Jiangjie Qin edited comment on KAFKA-3256 at 2/22/16 9:23 PM: -- Thanks for the

[jira] [Commented] (KAFKA-3256) Large number of system test failures

[ https://issues.apache.org/jira/browse/KAFKA-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157715#comment-15157715 ] Jiangjie Qin commented on KAFKA-3256: - Thanks for the investigation [~apovzner]. It looks upgrade test

[GitHub] kafka pull request: HOTFIX: make sure to go through all shutdown s...

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

[GitHub] kafka pull request: MINOR: Update streams RocksDb to 4.1.0

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

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

See Changes: [me] KAFKA-3255: Added unit tests for NetworkClient.connectionDelay(Node -- [...truncated 2642 lines...] kafka.integration.SslTopicMetadataTest > testAutoCreateTopic PASSED

[jira] [Commented] (KAFKA-3256) Large number of system test failures

[ https://issues.apache.org/jira/browse/KAFKA-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157604#comment-15157604 ] Anna Povzner commented on KAFKA-3256: - [~becket_qin], [~ijuma], [~geoffra] The remaining system tests

[jira] [Commented] (KAFKA-3256) Large number of system test failures

[ https://issues.apache.org/jira/browse/KAFKA-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15157580#comment-15157580 ] Jiangjie Qin commented on KAFKA-3256: - [~geoffra] It seems that yesterday's build had two tests

[GitHub] kafka pull request: MINOR: Example style improvements

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

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

GitHub user hachikuji reopened a pull request: https://github.com/apache/kafka/pull/920 KAFKA-3093: Add Connect status tracking API You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-3093 Alternatively you

[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=15157534#comment-15157534 ] ASF GitHub Bot commented on KAFKA-3093: --- Github user hachikuji closed the pull request at:

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

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

Github user hachikuji 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] [Commented] (KAFKA-3248) AdminClient Blocks Forever in send Method

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

[GitHub] kafka pull request: KAFKA-3248: AdminClient Blocks Forever in send...

GitHub user WarrenGreen opened a pull request: https://github.com/apache/kafka/pull/946 KAFKA-3248: AdminClient Blocks Forever in send Method Block while in bounds of timeout Author: Warren Green You can merge this pull request into a Git

[jira] [Updated] (KAFKA-3255) Extra unit tests for NetworkClient.connectionDelay(Node node, long now)

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

[jira] [Commented] (KAFKA-3255) Extra unit tests for NetworkClient.connectionDelay(Node node, long now)

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

[GitHub] kafka pull request: KAFKA-3255 Added unit tests for NetworkClient....

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/941 --- 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] [Created] (KAFKA-3260) Increase the granularity of commit for SourceTask

Jeremy Custenborder created KAFKA-3260: -- Summary: Increase the granularity of commit for SourceTask Key: KAFKA-3260 URL: https://issues.apache.org/jira/browse/KAFKA-3260 Project: Kafka

Re: When to use advertised.host.name ?

Hi Eugene, First, please post questions like this to the users list in the future. The dev list is much busier and it's easier for your email to get lost. And, this list is meant for development on Kafka internals. As far as your question, EC2 is a great example of when you may want to configure

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

+1 on deprecating old producer. On Mon, Feb 22, 2016 at 9:36 AM, Ismael Juma wrote: > Hi all, > > The new Java producer was introduced in 0.8.2.0 (released in February > 2015). It has become the default implementation for various tools since > 0.9.0.0 (released in October

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

Hi Jun, I think it makes sense to implement KIP-47 after KIP-33 so we can make it work for both LogAppendTime and CreateTime. And yes, I'm actively working on KIP-33. I had a voting thread on KIP-33 before and I'll bump it up. Thanks, Jiangjie (Becket) Qin On Mon, Feb 22, 2016 at 9:11 AM,

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

Hi all, The new Java producer was introduced in 0.8.2.0 (released in February 2015). It has become the default implementation for various tools since 0.9.0.0 (released in October 2015) and it is the only implementation with support for the security features introduced in 0.9.0.0. Given this, I

[jira] [Commented] (KAFKA-1476) Get a list of consumer groups

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

[GitHub] kafka pull request: tidy up spacing for ConsumerGroupCommand relat...

GitHub user christian-posta opened a pull request: https://github.com/apache/kafka/pull/945 tidy up spacing for ConsumerGroupCommand related to KAFKA-1476 … https://issues.apache.org/jira/browse/KAFKA-1476 Let me know if these kind of contributions should have their own

[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 ] Vahid Hashemian updated KAFKA-2832: --- Status: Patch Available (was: Open) > support exclude.internal.topics in new consumer >

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

Becket, Since you submitted KIP-33, are you actively working on that? If so, it would make sense to implement KIP-47 after KIP-33 so that it works for both CreateTime and LogAppendTime. Thanks, Jun On Fri, Feb 19, 2016 at 6:25 PM, Bill Warshaw wrote: > Hi Jun, > > 1.

[GitHub] kafka pull request: [WIP] Support multiple DNS entries for a given...

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

Wondering the process for pushing changes to the website/documentation? I see the docs in HTML format in the github, but I also notice the version on the website is slightly lagging the version in the source. How do those sync up? What's the process to initiate changes to doc? Thanks! --

[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: --- Reviewer: Jun Rao Status: Patch Available (was: Open) > Skip duplicate message size check if

[jira] [Updated] (KAFKA-3259) KIP-31/KIP-32 clean-ups

[ https://issues.apache.org/jira/browse/KAFKA-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3259: --- Reviewer: Jun Rao Status: Patch Available (was: Open) > KIP-31/KIP-32 clean-ups >

[jira] [Commented] (KAFKA-3251) Requesting committed offsets results in inconsistent results

[ https://issues.apache.org/jira/browse/KAFKA-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15156819#comment-15156819 ] Dimitrij Denissenko commented on KAFKA-3251: Looks like it's fixed 0.9.0.1. Thanks >

Kafka basic doubts

Hi All, Greetings..!!! This is my first email to Kafka Community. I have just started exploring Kafka on CDH5.5 cluster which ships with Kafka 0.8.2.1. I am able to run sample programs for producer as well as consumer (both high level and low level). Now I am trying to load messages from Kafka

Random email

Apologies for the random email, sent to the wrong mailing list. Please ignore...

Recall: Engine team

Simon Cooper would like to recall the message, "Engine team".

Engine team

Me: - Last week: o DB byte arrays refactor done o Last week did some work on the zapp performance issues, currently blocked as cluster is being used o Also lots of bugfixes around sandbox - This week: o Follow up tasks for byte arrays refactor o Looking at

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

[ https://issues.apache.org/jira/browse/KAFKA-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3258: -- Status: Patch Available (was: Open) > BrokerTopicMetrics of deleted topics are never deleted >

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

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

[GitHub] kafka pull request: KAFKA-3258: Delete broker topic metrics of del...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/944 KAFKA-3258: Delete broker topic metrics of deleted topics Delete per-topic metrics when there are no replicas of any partitions of the topic on a broker. You can merge this pull request into

[jira] [Commented] (KAFKA-3259) KIP-31/KIP-32 clean-ups

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

[GitHub] kafka pull request: KAFKA-3259 KAFKA-3253; KIP-31/KIP-32 Follow-up

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/943 KAFKA-3259 KAFKA-3253; KIP-31/KIP-32 Follow-up You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka kafka-3259-kip-31-32-clean-ups

[jira] [Created] (KAFKA-3259) KIP-31/KIP-32 clean-ups

Ismael Juma created KAFKA-3259: -- Summary: KIP-31/KIP-32 clean-ups Key: KAFKA-3259 URL: https://issues.apache.org/jira/browse/KAFKA-3259 Project: Kafka Issue Type: Improvement

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

Rajini Sivaram created KAFKA-3258: - Summary: BrokerTopicMetrics of deleted topics are never deleted Key: KAFKA-3258 URL: https://issues.apache.org/jira/browse/KAFKA-3258 Project: Kafka Issue