[jira] [Updated] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Cheng updated KAFKA-3042: --- Attachment: state-change.log server.log.2016-03-23-01 controller.log

Request for edit access to Kafka wiki

Hi All, I want to publish C++ Kafka client. I have my git repository ready. Now I want add entry on Kafka “Clients” page (Confluence wiki page) for this new client. I did create my login for the Confluence and login with that. But I am not able to edit the page. Do I require to do some other

[jira] [Updated] (KAFKA-3448) IPV6 Regex is missing % character

[ https://issues.apache.org/jira/browse/KAFKA-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Soumyajit Sahu updated KAFKA-3448: -- Fix Version/s: 0.10.1.0 Status: Patch Available (was: Open) > IPV6 Regex is missing

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

See Changes: [cshapi] KAFKA-3431: Remove `o.a.k.common.BrokerEndPoint` in favour of `Node` -- [...truncated 7550 lines...] org.apache.kafka.streams.kstream.internals.KTableKTableOuterJoinTest

[jira] [Commented] (KAFKA-3448) IPV6 Regex is missing % character

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

[GitHub] kafka pull request: KAFKA-3448: add % character to ipv6 regex

GitHub user soumyajit-sahu opened a pull request: https://github.com/apache/kafka/pull/1120 KAFKA-3448: add % character to ipv6 regex IPV6 address can contain % character You can merge this pull request into a Git repository by running: $ git pull

Build failed in Jenkins: kafka-0.10-jdk7 #7

See Changes: [cshapi] KAFKA-3431: Remove `o.a.k.common.BrokerEndPoint` in favour of `Node` -- [...truncated 1591 lines...] kafka.integration.AutoOffsetResetTest > testResetToLatestWhenOffsetTooLow

[jira] [Commented] (KAFKA-3448) IPV6 Regex is missing % character

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

[GitHub] kafka pull request: KAFKA-3448: Include % character in IPV6 Regex

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

[jira] [Commented] (KAFKA-3448) IPV6 Regex is missing % character

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

[GitHub] kafka pull request: KAFKA-3448: Include % character in IPV6 Regex

GitHub user soumyajit-sahu opened a pull request: https://github.com/apache/kafka/pull/1119 KAFKA-3448: Include % character in IPV6 Regex IPV6 addresses could have the % character. When an address is written textually, the zone index is appended to the address, separated by a

[jira] [Created] (KAFKA-3448) IPV6 Regex is missing % character

Soumyajit Sahu created KAFKA-3448: - Summary: IPV6 Regex is missing % character Key: KAFKA-3448 URL: https://issues.apache.org/jira/browse/KAFKA-3448 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-3431) Remove `o.a.k.common.BrokerEndPoint` in favour of `Node`

[ https://issues.apache.org/jira/browse/KAFKA-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3431: --- Description: No point in having two classes that are basically the same. The former was introduced

[jira] [Commented] (KAFKA-3431) Move `BrokerEndPoint` from `o.a.k.common` to `o.a.k.common.internals`

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

[jira] [Updated] (KAFKA-3431) Remove `o.a.k.common.BrokerEndPoint` in favour of `Node`

[ https://issues.apache.org/jira/browse/KAFKA-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3431: --- Summary: Remove `o.a.k.common.BrokerEndPoint` in favour of `Node` (was: Move `BrokerEndPoint` from

[GitHub] kafka pull request: KAFKA-3431; Move `BrokerEndPoint` from `o.a.k....

Github user ijuma closed the pull request at: https://github.com/apache/kafka/pull/1102 --- 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-3431) Move `BrokerEndPoint` from `o.a.k.common` to `o.a.k.common.internals`

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

[jira] [Commented] (KAFKA-3431) Move `BrokerEndPoint` from `o.a.k.common` to `o.a.k.common.internals`

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

[GitHub] kafka pull request: KAFKA-3431: Remove `o.a.k.common.BrokerEndPoin...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1105 --- 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-3432) Cluster.update() thread-safety

[ https://issues.apache.org/jira/browse/KAFKA-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3432: --- Reviewer: Guozhang Wang Status: Patch Available (was: Open) > Cluster.update() thread-safety >

[jira] [Commented] (KAFKA-3432) Cluster.update() thread-safety

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

[GitHub] kafka pull request: KAFKA-3432; Cluster.update() thread-safety

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1118 KAFKA-3432; Cluster.update() thread-safety Replace `update` with `withPartitions`, which returns a copy instead of mutating the instance. You can merge this pull request into a Git repository by

[jira] [Commented] (KAFKA-3447) partitionState in UpdateMetadataRequest not logged properly state-change log

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

[jira] [Updated] (KAFKA-3447) partitionState in UpdateMetadataRequest not logged properly state-change log

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

[GitHub] kafka pull request: KAFKA-3447; partitionState in UpdateMetadataRe...

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

Fallout from upgrading to kafka 0.9.0.0 from 0.8.2.1

Hi folks, Rajiv, Jun, I'd like to bring up this thread again from Rajiv Kurian 3 months ago. Basically we did the same thing as Rajiv did. I upgraded two machines (out of 10) from 0.8.2.1 to 0.9. SO after the upgrade, there will be 2 machines in 0.9 and 8 machines in 0.8.2.1. And initially it all

[jira] [Commented] (KAFKA-3432) Cluster.update() thread-safety

[ https://issues.apache.org/jira/browse/KAFKA-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15207622#comment-15207622 ] Ismael Juma commented on KAFKA-3432: That sounds better [~guozhang], I'll give it a try. >

[jira] [Updated] (KAFKA-3447) partitionState in UpdateMetadataRequest not logged properly state-change log

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

[jira] [Commented] (KAFKA-3447) partitionState in UpdateMetadataRequest not logged properly state-change log

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

[GitHub] kafka pull request: KAFKA-3447; partitionState in UpdateMetadataRe...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1117 KAFKA-3447; partitionState in UpdateMetadataRequest not logged properly state-change log You can merge this pull request into a Git repository by running: $ git pull

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

See

[jira] [Assigned] (KAFKA-3447) partitionState in UpdateMetadataRequest not logged properly state-change log

[ https://issues.apache.org/jira/browse/KAFKA-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3447: -- Assignee: Ismael Juma > partitionState in UpdateMetadataRequest not logged properly

[jira] [Created] (KAFKA-3447) partitionState in UpdateMetadataRequest not logged properly state-change log

Jun Rao created KAFKA-3447: -- Summary: partitionState in UpdateMetadataRequest not logged properly state-change log Key: KAFKA-3447 URL: https://issues.apache.org/jira/browse/KAFKA-3447 Project: Kafka

Re: [VOTE] KIP-51 - List Connectors REST API

+1 (binding) On Tue, Mar 22, 2016 at 3:56 PM, Liquan Pei wrote: > +1 > > On Tue, Mar 22, 2016 at 3:54 PM, Gwen Shapira wrote: > > > +1 > > > > Straight forward enough and can't possibly break anything. > > > > On Tue, Mar 22, 2016 at 3:46 PM, Ewen

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

See

[jira] [Assigned] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-3177: -- Assignee: Jason Gustafson (was: Jiangjie Qin) > Kafka consumer can hang when

Re: [VOTE] KIP-51 - List Connectors REST API

+1 On Tue, Mar 22, 2016 at 3:54 PM, Gwen Shapira wrote: > +1 > > Straight forward enough and can't possibly break anything. > > On Tue, Mar 22, 2016 at 3:46 PM, Ewen Cheslack-Postava > wrote: > > > Since it's pretty minimal, we'd like to squeeze it into

Re: [VOTE] KIP-51 - List Connectors REST API

+1 Straight forward enough and can't possibly break anything. On Tue, Mar 22, 2016 at 3:46 PM, Ewen Cheslack-Postava wrote: > Since it's pretty minimal, we'd like to squeeze it into 0.10 if possible, > and VOTE threads take 3 days, it was suggested it might make sense to

Re: [VOTE] KIP-51 - List Connectors REST API

+1 (non-binding) On Tue, Mar 22, 2016 at 3:46 PM, Ewen Cheslack-Postava wrote: > Since it's pretty minimal, we'd like to squeeze it into 0.10 if possible, > and VOTE threads take 3 days, it was suggested it might make sense to just > kick off voting on this KIP immediately

[VOTE] KIP-51 - List Connectors REST API

Since it's pretty minimal, we'd like to squeeze it into 0.10 if possible, and VOTE threads take 3 days, it was suggested it might make sense to just kick off voting on this KIP immediately (and restart it if someone raises an issue). Feel free to object and comment in the DISCUSS thread if you

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

See Changes: [cshapi] KAFKA-3435: Follow up to fix checkstyle -- [...truncated 1621 lines...] kafka.consumer.ZookeeperConsumerConnectorTest > testConsumerDecoder PASSED

[jira] [Commented] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15207431#comment-15207431 ] Jiangjie Qin commented on KAFKA-3177: - [~hachikuji] It would be great if you can help. I probably

Jenkins build is back to normal : kafka-0.10-jdk7 #4

See

[jira] [Commented] (KAFKA-3301) CommonClientConfigs.METRICS_SAMPLE_WINDOW_MS_DOC is incorrect

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

[jira] [Updated] (KAFKA-3301) CommonClientConfigs.METRICS_SAMPLE_WINDOW_MS_DOC is incorrect

[ https://issues.apache.org/jira/browse/KAFKA-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3301: --- Resolution: Fixed Fix Version/s: (was: 0.10.1.0) 0.10.0.0 Status:

[GitHub] kafka pull request: KAFKA-3301: CommonClientConfigs.METRICS_SAMPLE...

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

See Changes: [cshapi] KAFKA-3426; Improve protocol type errors when invalid sizes are [wangguoz] KAFKA-3319: improve session timeout broker/client config documentation [cshapi] KAFKA-3219: Fix long topic name validation

Re: [DISCUSS] KIP-51 - List Connectors REST API

Yeah, we can do that. Not sure what we might want to add there, but makes sense to keep things flexible. Updated the KIP text to reflect this. -Ewen On Tue, Mar 22, 2016 at 2:51 PM, Jason Gustafson wrote: > Hey Ewen, > > Just a quick question. It looks like we're returning

Re: [DISCUSS] KIP-51 - List Connectors REST API

Hey Ewen, Just a quick question. It looks like we're returning a simple array containing the classnames. Would it make sense to return a set of objects instead? For example: [ { "class": "org.apache.kafka.connect.file.FileStreamSourceConnector"}, { "class":

[DISCUSS] KIP-51 - List Connectors REST API

Hi all, It was pointed out that we've been playing a bit fast and loose with API additions in Kafka. I think it's worth discussing a lighter weight process for APIs that are still marked unstable, but for the time being we'll add KIPs before adjusting these APIs. To that end, I'd like to discuss

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

See Changes: [wangguoz] KAFKA-3319: improve session timeout broker/client config documentation [cshapi] KAFKA-3219: Fix long topic name validation -- [...truncated 3517 lines...]

[jira] [Commented] (KAFKA-3435) Remove `Unstable` annotation from new Java Consumer

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

[GitHub] kafka pull request: KAFKA-3435: Follow up to fix checkstyle

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1116 --- 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-3435) Remove `Unstable` annotation from new Java Consumer

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

[GitHub] kafka pull request: KAFKA-3435: Follow up to fix checkstyle

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/1116 KAFKA-3435: Follow up to fix checkstyle You can merge this pull request into a Git repository by running: $ git pull https://github.com/ewencp/kafka kafka-3435-follow-up Alternatively you can

Build failed in Jenkins: kafka-0.10-jdk7 #3

See Changes: [cshapi] KAFKA-3426; Improve protocol type errors when invalid sizes are received -- [...truncated 5446 lines...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[1] PASSED

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

See Changes: [cshapi] KAFKA-3435: Remove `Unstable` annotation from new Java Consumer [cshapi] MINOR: Remove the very misleading comment lines [cshapi] KAFKA-3426; Improve protocol type errors when invalid sizes are received

[jira] [Commented] (KAFKA-3409) Mirror maker hangs indefinitely due to commit

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

[GitHub] kafka pull request: KAFKA-3409: handle CommitFailedException in Mi...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1115 KAFKA-3409: handle CommitFailedException in MirrorMaker You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-3409

[jira] [Commented] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15207225#comment-15207225 ] Jason Gustafson commented on KAFKA-3177: [~becket_qin] Were you planning to submit a patch for

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

See Changes: [cshapi] KAFKA-3435: Remove `Unstable` annotation from new Java Consumer [cshapi] MINOR: Remove the very misleading comment lines -- [...truncated 5378 lines...]

[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 ] Gwen Shapira updated KAFKA-3219: Resolution: Fixed Fix Version/s: 0.10.0.0 Status: Resolved (was: Patch Available)

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

[jira] [Resolved] (KAFKA-3319) Improve session timeout broker and client configuration documentation

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

[GitHub] kafka pull request: KAFKA-3219: Fix long topic name validation

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/898 --- 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-3319) Improve session timeout broker and client configuration documentation

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

Build failed in Jenkins: kafka-0.10-jdk7 #2

See Changes: [cshapi] KAFKA-3435: Remove `Unstable` annotation from new Java Consumer [cshapi] MINOR: Remove the very misleading comment lines -- [...truncated 3119 lines...]

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15207142#comment-15207142 ] Dana Powers commented on KAFKA-3442: sounds good to me! > FetchResponse size exceeds

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15207127#comment-15207127 ] Jiangjie Qin commented on KAFKA-3442: - [~dana.powers] I think we all agree that having an explicit

[jira] [Updated] (KAFKA-3426) Improve protocol type errors when invalid sizes are received

[ https://issues.apache.org/jira/browse/KAFKA-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3426: Resolution: Fixed Fix Version/s: 0.10.0.0 0.10.1.0 Status:

[jira] [Commented] (KAFKA-3426) Improve protocol type errors when invalid sizes are received

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

[GitHub] kafka pull request: KAFKA-3426; Improve protocol type errors when ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1100 --- 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: Remove the very misleading comment line...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/793 --- 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-3435) Remove `Unstable` annotation from new Java Consumer

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

[jira] [Commented] (KAFKA-3435) Remove `Unstable` annotation from new Java Consumer

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

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

[ https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15206956#comment-15206956 ] Jun Rao commented on KAFKA-3296: [~thecoop1984], it's a bit weird that that the controller doesn't contain

[jira] [Commented] (KAFKA-3210) Using asynchronous calls through the raw ZK API in ZkUtils

[ https://issues.apache.org/jira/browse/KAFKA-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15206935#comment-15206935 ] Flavio Junqueira commented on KAFKA-3210: - [~granthenke] my main goal here is to have access to

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

[ https://issues.apache.org/jira/browse/KAFKA-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KAFKA-3367. Resolution: Not A Problem > Delete topic dont delete the complete log from kafka >

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15206876#comment-15206876 ] Dana Powers commented on KAFKA-3442: [~junrao] Actually I meant adding the error code to v0 and v1

[jira] [Assigned] (KAFKA-3417) Invalid characters in config properties not being validated?

[ https://issues.apache.org/jira/browse/KAFKA-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke reassigned KAFKA-3417: -- Assignee: Grant Henke > Invalid characters in config properties not being validated? >

[jira] [Updated] (KAFKA-3426) Improve protocol type errors when invalid sizes are received

[ https://issues.apache.org/jira/browse/KAFKA-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3426: --- Affects Version/s: 0.9.0.0 > Improve protocol type errors when invalid sizes are received >

Jenkins job for 0.10.0

Hi Team Kafka, Just a quick update - I've created a Jenkins job to test the 0.10.0 branch, to make sure we don't accidentally break it :) I know our tests have been all over the place recently, so this may not be as useful as it should be - but it is worth taking a look at the tests to make sure

[jira] [Comment Edited] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15206808#comment-15206808 ] Jiangjie Qin edited comment on KAFKA-3442 at 3/22/16 5:42 PM: -- [~junrao] Yes,

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15206867#comment-15206867 ] Jun Rao commented on KAFKA-3442: [~becket_qin], it's probably better if we keep supporting the current

[GitHub] kafka pull request: KAFKA-3301: CommonClientConfigs.METRICS_SAMPLE...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/1114 KAFKA-3301: CommonClientConfigs.METRICS_SAMPLE_WINDOW_MS_DOC is incor… …rect You can merge this pull request into a Git repository by running: $ git pull

[jira] [Updated] (KAFKA-3301) CommonClientConfigs.METRICS_SAMPLE_WINDOW_MS_DOC is incorrect

[ https://issues.apache.org/jira/browse/KAFKA-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3301: --- Status: Patch Available (was: Open) > CommonClientConfigs.METRICS_SAMPLE_WINDOW_MS_DOC is incorrect

[jira] [Commented] (KAFKA-3301) CommonClientConfigs.METRICS_SAMPLE_WINDOW_MS_DOC is incorrect

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

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15206838#comment-15206838 ] Magnus Edenhill commented on KAFKA-3442: librdkafka silently ignores partial messages (which are

[jira] [Commented] (KAFKA-3409) Mirror maker hangs indefinitely due to commit

[ https://issues.apache.org/jira/browse/KAFKA-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15206820#comment-15206820 ] Jason Gustafson commented on KAFKA-3409: [~singhashish] Thanks! The thing that's bugging me is

[jira] [Commented] (KAFKA-3409) Mirror maker hangs indefinitely due to commit

[ https://issues.apache.org/jira/browse/KAFKA-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15206800#comment-15206800 ] Ashish K Singh commented on KAFKA-3409: --- [~hachikuji] there is a trivial patch,

[jira] [Assigned] (KAFKA-3301) CommonClientConfigs.METRICS_SAMPLE_WINDOW_MS_DOC is incorrect

[ https://issues.apache.org/jira/browse/KAFKA-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke reassigned KAFKA-3301: -- Assignee: Grant Henke > CommonClientConfigs.METRICS_SAMPLE_WINDOW_MS_DOC is incorrect >

[jira] [Commented] (KAFKA-3442) FetchResponse size exceeds max.partition.fetch.bytes

[ https://issues.apache.org/jira/browse/KAFKA-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15206790#comment-15206790 ] Dana Powers commented on KAFKA-3442: yes, kafka-python uses the same check for partial messages as the

[jira] [Updated] (KAFKA-3438) Rack Aware Replica Reassignment should warn of overloaded brokers

[ https://issues.apache.org/jira/browse/KAFKA-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3438: --- Fix Version/s: 0.10.0.1 > Rack Aware Replica Reassignment should warn of overloaded brokers >

[jira] [Updated] (KAFKA-3438) Rack Aware Replica Reassignment should warn of overloaded brokers

[ https://issues.apache.org/jira/browse/KAFKA-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3438: --- Affects Version/s: 0.10.0.0 > Rack Aware Replica Reassignment should warn of overloaded brokers >

[jira] [Updated] (KAFKA-3437) We don't need sitedocs package for every scala version

[ https://issues.apache.org/jira/browse/KAFKA-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3437: --- Affects Version/s: 0.9.0.0 > We don't need sitedocs package for every scala version >

[jira] [Updated] (KAFKA-3437) We don't need sitedocs package for every scala version

[ https://issues.apache.org/jira/browse/KAFKA-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3437: --- Fix Version/s: 0.10.0.1 > We don't need sitedocs package for every scala version >

[jira] [Assigned] (KAFKA-3437) We don't need sitedocs package for every scala version

[ https://issues.apache.org/jira/browse/KAFKA-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke reassigned KAFKA-3437: -- Assignee: Grant Henke > We don't need sitedocs package for every scala version >

[jira] [Work started] (KAFKA-3409) Mirror maker hangs indefinitely due to commit

[ https://issues.apache.org/jira/browse/KAFKA-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3409 started by Jason Gustafson. -- > Mirror maker hangs indefinitely due to commit >

[jira] [Updated] (KAFKA-3445) ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit

[ https://issues.apache.org/jira/browse/KAFKA-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-3445: -- Status: Patch Available (was: Open) > ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit >

[jira] [Updated] (KAFKA-3441) 0.10.0 documentation still says "0.9.0"

[ https://issues.apache.org/jira/browse/KAFKA-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3441: --- Affects Version/s: 0.10.0.0 > 0.10.0 documentation still says "0.9.0" >

  1   2   >