[jira] [Created] (KAFKA-3222) SslProducerSendTest transient failure.

Jiangjie Qin created KAFKA-3222: --- Summary: SslProducerSendTest transient failure. Key: KAFKA-3222 URL: https://issues.apache.org/jira/browse/KAFKA-3222 Project: Kafka Issue Type: Sub-task

Jenkins build is back to normal : kafka_0.9.0_jdk7 #116

See

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

See Changes: [me] HOTFIX: RecordCollector should send a record to the specified partition [me] HOTFIX: open window segments on init [me] KAFKA-3191: Improve offset committing JavaDoc in KafkaConsumer -

[jira] [Commented] (KAFKA-3055) JsonConverter mangles schema during serialization (fromConnectData)

[ https://issues.apache.org/jira/browse/KAFKA-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138155#comment-15138155 ] Ewen Cheslack-Postava commented on KAFKA-3055: -- There's a config schemas.cach

[jira] [Updated] (KAFKA-3191) Improve offset committing JavaDoc in KafkaConsumer

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

[jira] [Commented] (KAFKA-3191) Improve offset committing JavaDoc in KafkaConsumer

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

[GitHub] kafka pull request: KAFKA-3191: Improve offset committing JavaDoc ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/850 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

[GitHub] kafka pull request: HOTFIX: open window segments on init

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/886 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

[jira] [Updated] (KAFKA-3217) Unit tests which dont close producers auto-create topics in Kafka brokers of other tests when port is reused

[ https://issues.apache.org/jira/browse/KAFKA-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3217: --- Fix Version/s: (was: 0.9.0.1) 0.9.1.0 > Unit tests which dont close producers a

[jira] [Updated] (KAFKA-3217) Unit tests which dont close producers auto-create topics in Kafka brokers of other tests when port is reused

[ https://issues.apache.org/jira/browse/KAFKA-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3217: --- Fix Version/s: 0.9.0.1 Status: Patch Available (was: Open) > Unit tests which dont close p

[GitHub] kafka pull request: HOTFIX: RecordCollector should send a record t...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/887 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

[jira] [Commented] (KAFKA-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&focusedCommentId=15138093#comment-15138093 ] Jason Gustafson commented on KAFKA-3093: [~jinxing6...@126.com] I'm going to go ah

Want to speak at Apache Kafka meetup at LinkedIn on February 23?

Hi Friends of Kafka, Doing anything cool with Kafka? Looking to share?! LinkedIn will host an Apache Kafka meetup in Mountain View CA on the evening of Tuesday, February 23. We currently have 2-talks figured out but would like to

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

[ https://issues.apache.org/jira/browse/KAFKA-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138083#comment-15138083 ] Ismael Juma commented on KAFKA-3219: Makes sense, thanks. > Long topic names mess up

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

[ https://issues.apache.org/jira/browse/KAFKA-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138080#comment-15138080 ] Vahid Hashemian commented on KAFKA-3219: I see similar behavior when producing a n

[jira] [Commented] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

[ https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138038#comment-15138038 ] Rajiv Kurian commented on KAFKA-3159: - I'll try it tomorrow for sure. > Kafka consume

[jira] [Commented] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

[ https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138031#comment-15138031 ] Ismael Juma commented on KAFKA-3159: [~ra...@signalfx.com], when you get a chance to t

[jira] [Updated] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

[ https://issues.apache.org/jira/browse/KAFKA-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3159: --- Reviewer: Jun Rao Status: Patch Available (was: Open) > Kafka consumer 0.9.0.0 client poll is

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

[ https://issues.apache.org/jira/browse/KAFKA-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137998#comment-15137998 ] Ismael Juma commented on KAFKA-3219: Seems sensible to fail with a reasonable error if

[jira] [Commented] (KAFKA-3221) kafka-acls.sh must verify if a user has sufficient privileges to perform acls CRUD

[ https://issues.apache.org/jira/browse/KAFKA-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137989#comment-15137989 ] Ashish K Singh commented on KAFKA-3221: --- [~ijuma] true, updated description. > kafk

[jira] [Updated] (KAFKA-3221) kafka-acls.sh must verify if a user has sufficient privileges to perform acls CRUD

[ https://issues.apache.org/jira/browse/KAFKA-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3221: -- Description: kafka-acls.sh provides an insecure entry point to Kafka's authorization. No checks

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

[ https://issues.apache.org/jira/browse/KAFKA-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137981#comment-15137981 ] Vahid Hashemian commented on KAFKA-3219: This seems to be somehow related to folde

[jira] [Updated] (KAFKA-3221) kafka-acls.sh must verify if a user has sufficient privileges to perform acls CRUD

[ https://issues.apache.org/jira/browse/KAFKA-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3221: -- Affects Version/s: 0.9.0.0 > kafka-acls.sh must verify if a user has sufficient privileges to pe

[GitHub] kafka pull request: HOTFIX: RecordCollector should send a record t...

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/887 HOTFIX: RecordCollector should send a record to the specified partition @guozhangwang You can merge this pull request into a Git repository by running: $ git pull https://github.com/ymatsuda/

[jira] [Commented] (KAFKA-3221) kafka-acls.sh must verify if a user has sufficient privileges to perform acls CRUD

[ https://issues.apache.org/jira/browse/KAFKA-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137901#comment-15137901 ] Ismael Juma commented on KAFKA-3221: You didn't mention ZooKeeper authentication in yo

[jira] [Created] (KAFKA-3221) kafka-acls.sh must verify if a user has sufficient privileges to perform acls CRUD

Ashish K Singh created KAFKA-3221: - Summary: kafka-acls.sh must verify if a user has sufficient privileges to perform acls CRUD Key: KAFKA-3221 URL: https://issues.apache.org/jira/browse/KAFKA-3221 Pr

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

See

[GitHub] kafka pull request: HOTFIX: open window segments on init

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/886 HOTFIX: open window segments on init @guozhangwang A window store should open all existing segments. This is important for segment cleanup, and it also ensures that the first fetch() call

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

[ https://issues.apache.org/jira/browse/KAFKA-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137686#comment-15137686 ] Vahid Hashemian commented on KAFKA-3219: My apologies. I tried again, and noticed

[GitHub] kafka pull request: MINOR: fix RocksDBStore range search

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/883 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

[jira] [Created] (KAFKA-3220) Failure in kafka.server.ClientQuotaManagerTest.testQuotaViolation

Guozhang Wang created KAFKA-3220: Summary: Failure in kafka.server.ClientQuotaManagerTest.testQuotaViolation Key: KAFKA-3220 URL: https://issues.apache.org/jira/browse/KAFKA-3220 Project: Kafka

[GitHub] kafka pull request: HOTFIX: fix streams issues

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/877 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

[jira] [Assigned] (KAFKA-3218) Kafka-0.9.0.0 does not work as OSGi module

[ https://issues.apache.org/jira/browse/KAFKA-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-3218: - Assignee: Rajini Sivaram > Kafka-0.9.0.0 does not work as OSGi module > -

[jira] [Commented] (KAFKA-3218) Kafka-0.9.0.0 does not work as OSGi module

[ https://issues.apache.org/jira/browse/KAFKA-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137583#comment-15137583 ] Rajini Sivaram commented on KAFKA-3218: --- Not sure if a configuration option to choos

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

[ https://issues.apache.org/jira/browse/KAFKA-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137518#comment-15137518 ] Vahid Hashemian commented on KAFKA-3219: [~edenhill] I tried the same command abov

[GitHub] kafka pull request: MINOR: Use explicit type in AclCommand

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/885 MINOR: Use explicit type in AclCommand Inference sometimes fails for this case. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka use-expl

[jira] [Commented] (KAFKA-3186) Kafka authorizer should be aware of principal types it supports.

[ https://issues.apache.org/jira/browse/KAFKA-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137360#comment-15137360 ] Ashish K Singh commented on KAFKA-3186: --- [~gwenshap] mind taking a look at this. It

[jira] [Commented] (KAFKA-3141) kafka-acls.sh throws ArrayIndexOutOfBoundsException for an invalid authorizer-property

[ https://issues.apache.org/jira/browse/KAFKA-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137357#comment-15137357 ] Ashish K Singh commented on KAFKA-3141: --- [~gwenshap] mind taking a look at this. It

[jira] [Commented] (KAFKA-3159) Kafka consumer 0.9.0.0 client poll is very CPU intensive under certain conditions

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

[GitHub] kafka pull request: KAFKA-3159: stale high watermark segment offse...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/884 KAFKA-3159: stale high watermark segment offset causes early fetch return You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka K3159

[GitHub] kafka pull request: MINOR: fix RocksDBStore range search

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/883 MINOR: fix RocksDBStore range search The range is inclusive according to KeyValueStore's java doc. You can merge this pull request into a Git repository by running: $ git pull https://github.co

[jira] [Updated] (KAFKA-3186) Kafka authorizer should be aware of principal types it supports.

[ https://issues.apache.org/jira/browse/KAFKA-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3186: -- Affects Version/s: 0.9.0.0 > Kafka authorizer should be aware of principal types it supports. >

[jira] [Updated] (KAFKA-3141) kafka-acls.sh throws ArrayIndexOutOfBoundsException for an invalid authorizer-property

[ https://issues.apache.org/jira/browse/KAFKA-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3141: -- Fix Version/s: 0.9.0.1 > kafka-acls.sh throws ArrayIndexOutOfBoundsException for an invalid > a

[jira] [Updated] (KAFKA-3141) kafka-acls.sh throws ArrayIndexOutOfBoundsException for an invalid authorizer-property

[ https://issues.apache.org/jira/browse/KAFKA-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3141: -- Affects Version/s: 0.9.0.0 > kafka-acls.sh throws ArrayIndexOutOfBoundsException for an invalid

[jira] [Updated] (KAFKA-3186) Kafka authorizer should be aware of principal types it supports.

[ https://issues.apache.org/jira/browse/KAFKA-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3186: -- Fix Version/s: 0.9.0.1 > Kafka authorizer should be aware of principal types it supports. >

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

[ https://issues.apache.org/jira/browse/KAFKA-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-3219: -- Assignee: Vahid Hashemian > Long topic names mess up broker topic state > -

[jira] [Commented] (KAFKA-3218) Kafka-0.9.0.0 does not work as OSGi module

[ https://issues.apache.org/jira/browse/KAFKA-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137191#comment-15137191 ] Manikumar Reddy commented on KAFKA-3218: Thanks for reporting this. Can we add a n

[jira] [Commented] (KAFKA-2601) ConsoleProducer tool shows stacktrace on invalid command parameters

[ https://issues.apache.org/jira/browse/KAFKA-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137175#comment-15137175 ] Gabriel Nicolas Avellaneda commented on KAFKA-2601: --- [~mgainty] this is

[jira] [Commented] (KAFKA-2601) ConsoleProducer tool shows stacktrace on invalid command parameters

[ https://issues.apache.org/jira/browse/KAFKA-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137107#comment-15137107 ] Martin Gainty commented on KAFKA-2601: -- i cannot find https://github.com/apache/kafka

[jira] [Commented] (KAFKA-2375) Implement elasticsearch Copycat sink connector

[ https://issues.apache.org/jira/browse/KAFKA-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136869#comment-15136869 ] Artyom commented on KAFKA-2375: --- Hi, So me and my Team worked on this and implemented this

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

[ https://issues.apache.org/jira/browse/KAFKA-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Magnus Edenhill updated KAFKA-3219: --- Description: Seems like the broker doesn't like topic names of 254 chars or more when creatin

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

Magnus Edenhill created KAFKA-3219: -- Summary: Long topic names mess up broker topic state Key: KAFKA-3219 URL: https://issues.apache.org/jira/browse/KAFKA-3219 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-2295) Dynamically loaded classes (encoders, etc.) may not be found by Kafka Producer

[ https://issues.apache.org/jira/browse/KAFKA-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136818#comment-15136818 ] Joe O'Connor commented on KAFKA-2295: - This change appears to have caused KAFKA-3218,

[jira] [Updated] (KAFKA-3218) Kafka-0.9.0.0 does not work as OSGi module

[ https://issues.apache.org/jira/browse/KAFKA-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe O'Connor updated KAFKA-3218: Attachment: ContextClassLoaderBug.tar.gz Testcase attached in ContextClassLoaderBug.tar.gz , README.

[jira] [Created] (KAFKA-3218) Kafka-0.9.0.0 does not work as OSGi module

Joe O'Connor created KAFKA-3218: --- Summary: Kafka-0.9.0.0 does not work as OSGi module Key: KAFKA-3218 URL: https://issues.apache.org/jira/browse/KAFKA-3218 Project: Kafka Issue Type: Bug

Re: KAFKA-3002 issue in 0.9.0.0

Hi Roman, See the following email from Jun: http://search-hadoop.com/m/uyzND1nOVTTEB7pS&subj=Kafka+0+9+0+1+plan 0.9.0.1 will be out soon and it will include KAFKA-3002. Ismael On Mon, Feb 8, 2016 at 6:26 AM, Roman Hoc wrote: > Hello, > I got no answer from you side about this issue, therefor

[jira] [Commented] (KAFKA-3217) Unit tests which dont close producers auto-create topics in Kafka brokers of other tests when port is reused

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

[GitHub] kafka pull request: KAFKA-3217: Close producers in unit tests

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/882 KAFKA-3217: Close producers in unit tests Producers that are not closed auto-create topics in subsequent tests when Kafka server port is reused. Added missing close(). You can merge this pull

[jira] [Resolved] (KAFKA-2718) Reuse of temporary directories leading to transient unit test failures

[ https://issues.apache.org/jira/browse/KAFKA-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-2718. --- Resolution: Fixed There is another issue with the tests, not with directory reuse, but with a

[jira] [Commented] (KAFKA-3217) Unit tests which dont close producers auto-create topics in Kafka brokers of other tests when port is reused

[ https://issues.apache.org/jira/browse/KAFKA-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136688#comment-15136688 ] Ismael Juma commented on KAFKA-3217: Nice find! > Unit tests which dont close produce

[jira] [Created] (KAFKA-3217) Unit tests which dont close producers auto-create topics in Kafka brokers of other tests when port is reused

Rajini Sivaram created KAFKA-3217: - Summary: Unit tests which dont close producers auto-create topics in Kafka brokers of other tests when port is reused Key: KAFKA-3217 URL: https://issues.apache.org/jira/browse/