[jira] [Assigned] (KAFKA-3556) Improve group coordinator metrics

[ https://issues.apache.org/jira/browse/KAFKA-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei reassigned KAFKA-3556: - Assignee: Liquan Pei > Improve group coordinator metrics > - > >

[jira] [Resolved] (KAFKA-2479) Add CopycatExceptions to indicate transient and permanent errors in a connector/task

[ https://issues.apache.org/jira/browse/KAFKA-2479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei resolved KAFKA-2479. --- Resolution: Fixed > Add CopycatExceptions to indicate transient and permanent errors in a >

[jira] [Assigned] (KAFKA-3527) Consumer commitAsync should not expose internal exceptions

[ https://issues.apache.org/jira/browse/KAFKA-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei reassigned KAFKA-3527: - Assignee: Liquan Pei (was: Jason Gustafson) > Consumer commitAsync should not expose internal

[jira] [Assigned] (KAFKA-3457) KafkaConsumer.committed(...) hangs forever if port number is wrong

[ https://issues.apache.org/jira/browse/KAFKA-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei reassigned KAFKA-3457: - Assignee: Liquan Pei > KafkaConsumer.committed(...) hangs forever if port number is wrong >

[jira] [Reopened] (KAFKA-3605) Connector REST endpoint allows incorrectly overriding the connector name

[ https://issues.apache.org/jira/browse/KAFKA-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei reopened KAFKA-3605: --- > Connector REST endpoint allows incorrectly overriding the connector name >

[jira] [Resolved] (KAFKA-3605) Connector REST endpoint allows incorrectly overriding the connector name

[ https://issues.apache.org/jira/browse/KAFKA-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei resolved KAFKA-3605. --- Resolution: Fixed > Connector REST endpoint allows incorrectly overriding the connector name >

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

See

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

See Changes: [me] KAFKA-3606: Traverse CLASSPATH during herder start -- [...truncated 5326 lines...] org.apache.kafka.streams.processor.TopologyBuilderTest > testTopicGroupsByStateStore PASSED

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

See Changes: [wangguoz] KAFKA-3594; After calling MemoryRecords.close() method, hasRoomFor() -- [...truncated 717 lines...] kafka.server.KafkaConfigTest > testFromPropsInvalid PASSED

[jira] [Commented] (KAFKA-3606) Traverse CLASSPATH during herder start to list connectors

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

[jira] [Resolved] (KAFKA-3606) Traverse CLASSPATH during herder start to list connectors

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

[GitHub] kafka pull request: KAFKA-3606: Traverse CLASSPATH during herder s...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1252 --- 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-3607) Close state stores explicitly in unit tests upon completing

Guozhang Wang created KAFKA-3607: Summary: Close state stores explicitly in unit tests upon completing Key: KAFKA-3607 URL: https://issues.apache.org/jira/browse/KAFKA-3607 Project: Kafka

Re: [VOTE] KIP-35: Retrieve protocol version - Round 2

+1 (non binding) On Friday, 22 April 2016, Jason Gustafson wrote: > +1 (non-binding) > > On Thu, Apr 21, 2016 at 5:26 PM, Ewen Cheslack-Postava > > wrote: > > > +1 > > > > On Thu, Apr 21, 2016 at 5:25 PM, Guozhang Wang

Re: [VOTE] KIP-35: Retrieve protocol version - Round 2

+1 (non-binding) On Thu, Apr 21, 2016 at 5:26 PM, Ewen Cheslack-Postava wrote: > +1 > > On Thu, Apr 21, 2016 at 5:25 PM, Guozhang Wang wrote: > > > +1 > > > > On Thu, Apr 21, 2016 at 5:07 PM, Gwen Shapira wrote: > > > > > +1 > > > > >

[jira] [Commented] (KAFKA-3602) Rename RecordAccumulator dequeFor() and ensure proper usage

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

[GitHub] kafka pull request: KAFKA-3602: rename RecordAccumulator dequeFor(...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1254 KAFKA-3602: rename RecordAccumulator dequeFor() and fix usage You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-3602

Re: [VOTE] KIP-35: Retrieve protocol version - Round 2

+1 On Thu, Apr 21, 2016 at 5:25 PM, Guozhang Wang wrote: > +1 > > On Thu, Apr 21, 2016 at 5:07 PM, Gwen Shapira wrote: > > > +1 > > > > On Thu, Apr 21, 2016 at 4:48 PM, Ashish Singh > wrote: > > > Hey Guys, > > > > > > I would like

Re: [VOTE] KIP-35: Retrieve protocol version - Round 2

+1 On Thu, Apr 21, 2016 at 5:07 PM, Gwen Shapira wrote: > +1 > > On Thu, Apr 21, 2016 at 4:48 PM, Ashish Singh wrote: > > Hey Guys, > > > > I would like to re-initiate the voting process for *KIP-35: Retrieve > > protocol version*. > > > > KIP-35 can be

Re: [VOTE] KIP-35: Retrieve protocol version - Round 2

+1 On Thu, Apr 21, 2016 at 4:48 PM, Ashish Singh wrote: > Hey Guys, > > I would like to re-initiate the voting process for *KIP-35: Retrieve > protocol version*. > > KIP-35 can be accessed here >

[jira] [Created] (KAFKA-3606) Traverse CLASSPATH during herder start to list connectors

Liquan Pei created KAFKA-3606: - Summary: Traverse CLASSPATH during herder start to list connectors Key: KAFKA-3606 URL: https://issues.apache.org/jira/browse/KAFKA-3606 Project: Kafka Issue

[jira] [Commented] (KAFKA-3605) Connector REST endpoint allows incorrectly overriding the connector name

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

[GitHub] kafka pull request: KAFKA-3605: Return error if connector config i...

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/1253 KAFKA-3605: Return error if connector config includes mismatching connector name. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ewencp/kafka

[VOTE] KIP-35: Retrieve protocol version - Round 2

Hey Guys, I would like to re-initiate the voting process for *KIP-35: Retrieve protocol version*. KIP-35 can be accessed here . Following are a couple of related PRs. 1. KAFKA-3307: Add ApiVersion

Re: [DISCUSS] KIP-35 - Retrieve protocol version

Done. Thanks! On Thu, Apr 21, 2016 at 4:32 PM, Gwen Shapira wrote: > Lets start a vote immediately? We are short of time toward the release. > > On Thu, Apr 21, 2016 at 2:57 PM, Ashish Singh wrote: > > Hey Guys, > > > > KIP-35 > > < >

[GitHub] kafka pull request: Traverse CLASSPATH during herder start

GitHub user Ishiihara opened a pull request: https://github.com/apache/kafka/pull/1252 Traverse CLASSPATH during herder start @ewencp Can you take a quick look? You can merge this pull request into a Git repository by running: $ git pull https://github.com/Ishiihara/kafka

[jira] [Created] (KAFKA-3605) Connector REST endpoint allows incorrectly overriding the connector name

Ewen Cheslack-Postava created KAFKA-3605: Summary: Connector REST endpoint allows incorrectly overriding the connector name Key: KAFKA-3605 URL: https://issues.apache.org/jira/browse/KAFKA-3605

Re: [DISCUSS] KIP-50 - Enhance Authorizer interface to be aware of supported Principal Types

I would like to suggest taking the discussion of "how to break Kafka down into modules" outside the scope of KIP-50 and outside the scope of the next release. I understand that the current location of the authorizer API is not ideal, but I want to point out that the scope was already expanded

Re: [DISCUSS] KIP-35 - Retrieve protocol version

Lets start a vote immediately? We are short of time toward the release. On Thu, Apr 21, 2016 at 2:57 PM, Ashish Singh wrote: > Hey Guys, > > KIP-35 > > has been updated based on latest

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

See Changes: [wangguoz] KAFKA-3337: Extract selector as a separate groupBy operator for KTable [wangguoz] KAFKA-3589: set inner serializer for ChangedSerde upon initialization --

Re: Kafka Streams - read topic from beginning

Hello Maria, We have some thoughts about supporting finer grained flow controls in Kafka Streams https://issues.apache.org/jira/browse/KAFKA-3478 as part of a big effort to improve re-processing user experience, which covers this use case. We are shooting to have this post 0.10.0.0. As for now,

[jira] [Commented] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252935#comment-15252935 ] Vahid Hashemian commented on KAFKA-3144: [~Konrad Kalita], are you still working on this JIRA? If

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

See

[jira] [Updated] (KAFKA-3594) Kafka new producer retries doesn't work in 0.9.0.1

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

[jira] [Commented] (KAFKA-3594) Kafka new producer retries doesn't work in 0.9.0.1

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

[GitHub] kafka pull request: KAFKA-3594; After calling MemoryRecords.close(...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1249 --- 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-3602) Rename RecordAccumulator dequeFor() and ensure proper usage

[ https://issues.apache.org/jira/browse/KAFKA-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3602: - Summary: Rename RecordAccumulator dequeFor() and ensure proper usage (was: Rename

[jira] [Updated] (KAFKA-3602) Rename RecordAccumulator dequeFor() and ensure proper usage

[ https://issues.apache.org/jira/browse/KAFKA-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3602: - Description: In the investigation of KAFKA-3358, we found a case where the side effect of

Re: [DISCUSS] KIP-35 - Retrieve protocol version

Hey Guys, KIP-35 has been updated based on latest discussions and following PRs have also been updated. 1. KAFKA-3307: Add ApiVersion request/response and server side handling.

[jira] [Updated] (KAFKA-3600) Enhance java clients to use ApiVersion Req/Resp to check if the broker they are talking to supports required api versions

[ https://issues.apache.org/jira/browse/KAFKA-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3600: -- Fix Version/s: (was: 0.10.1.0) 0.10.0.0 > Enhance java clients to use

[jira] [Updated] (KAFKA-3307) Add ApiVersion request/response and server side handling.

[ https://issues.apache.org/jira/browse/KAFKA-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3307: -- Fix Version/s: 0.10.0.0 > Add ApiVersion request/response and server side handling. >

[GitHub] kafka pull request: KAFKA-3589: set inner serializer for ChangedSe...

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

[jira] [Commented] (KAFKA-3589) KTable.count(final KeyValueMapper<K, V, K1> selector, String name) throw NPE

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

[jira] [Created] (KAFKA-3604) Improve error messages when null is used with a non-nullable Type

Grant Henke created KAFKA-3604: -- Summary: Improve error messages when null is used with a non-nullable Type Key: KAFKA-3604 URL: https://issues.apache.org/jira/browse/KAFKA-3604 Project: Kafka

[jira] [Updated] (KAFKA-3600) Enhance java clients to use ApiVersion Req/Resp to check if the broker they are talking to supports required api versions

[ https://issues.apache.org/jira/browse/KAFKA-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3600: -- Status: Patch Available (was: Open) > Enhance java clients to use ApiVersion Req/Resp to check

[jira] [Resolved] (KAFKA-3589) KTable.count(final KeyValueMapper<K, V, K1> selector, String name) throw NPE

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

[jira] [Commented] (KAFKA-3601) fail fast when newer client connecting to older server

[ https://issues.apache.org/jira/browse/KAFKA-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252823#comment-15252823 ] Chris Pennello commented on KAFKA-3601: --- Noted. The brave new world has to start at some version.

[jira] [Created] (KAFKA-3603) Define HashCode and Equals methods for Schema, Field and Type

Grant Henke created KAFKA-3603: -- Summary: Define HashCode and Equals methods for Schema, Field and Type Key: KAFKA-3603 URL: https://issues.apache.org/jira/browse/KAFKA-3603 Project: Kafka

[jira] [Commented] (KAFKA-3601) fail fast when newer client connecting to older server

[ https://issues.apache.org/jira/browse/KAFKA-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252810#comment-15252810 ] Ashish K Singh commented on KAFKA-3601: --- [~cpennello_opentable] note that this won't help in case of

[jira] [Resolved] (KAFKA-3358) Only request metadata updates once we have topics or a pattern subscription

[ https://issues.apache.org/jira/browse/KAFKA-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-3358. Resolution: Won't Fix This will be fixed with the TopicMetadata changes in KIP-4. > Only

[jira] [Commented] (KAFKA-3358) Only request metadata updates once we have topics or a pattern subscription

[ https://issues.apache.org/jira/browse/KAFKA-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252794#comment-15252794 ] Jason Gustafson commented on KAFKA-3358: [~ijuma] [~granthenke] I've opened KAFKA-3602 to address

[jira] [Created] (KAFKA-3602) Rename RecordAccumulator dequeueFor() and ensure proper usage

Jason Gustafson created KAFKA-3602: -- Summary: Rename RecordAccumulator dequeueFor() and ensure proper usage Key: KAFKA-3602 URL: https://issues.apache.org/jira/browse/KAFKA-3602 Project: Kafka

[jira] [Commented] (KAFKA-3601) fail fast when newer client connecting to older server

[ https://issues.apache.org/jira/browse/KAFKA-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252788#comment-15252788 ] Chris Pennello commented on KAFKA-3601: --- Cool, thanks for the context. (I did search around before

[jira] [Commented] (KAFKA-3601) fail fast when newer client connecting to older server

[ https://issues.apache.org/jira/browse/KAFKA-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252777#comment-15252777 ] Ashish K Singh commented on KAFKA-3601: --- This might be addressed as part of KAFKA-3600. > fail fast

[jira] [Assigned] (KAFKA-3601) fail fast when newer client connecting to older server

[ https://issues.apache.org/jira/browse/KAFKA-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh reassigned KAFKA-3601: - Assignee: Ashish K Singh (was: Neha Narkhede) > fail fast when newer client connecting

[GitHub] kafka pull request: KAFKA-3600: Enhance java clients to use ApiVer...

GitHub user SinghAsDev opened a pull request: https://github.com/apache/kafka/pull/1251 KAFKA-3600: Enhance java clients to use ApiVersion Req/Resp to check if the broker they are talking to supports required api versions You can merge this pull request into a Git repository by

[jira] [Commented] (KAFKA-3600) Enhance java clients to use ApiVersion Req/Resp to check if the broker they are talking to supports required api versions

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

[jira] [Created] (KAFKA-3601) fail fast when newer client connecting to older server

Chris Pennello created KAFKA-3601: - Summary: fail fast when newer client connecting to older server Key: KAFKA-3601 URL: https://issues.apache.org/jira/browse/KAFKA-3601 Project: Kafka Issue

[jira] [Created] (KAFKA-3600) Enhance java clients to use ApiVersion Req/Resp to check if the broker they are talking to supports required api versions

Ashish K Singh created KAFKA-3600: - Summary: Enhance java clients to use ApiVersion Req/Resp to check if the broker they are talking to supports required api versions Key: KAFKA-3600 URL:

[GitHub] kafka pull request: KAFKA-3337: Extract selector as a separate gro...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1231 --- 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-3337) Extract selector as a separate groupBy operator for KTable aggregations

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

[jira] [Resolved] (KAFKA-3337) Extract selector as a separate groupBy operator for KTable aggregations

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

[jira] [Updated] (KAFKA-3307) Add ApiVersion request/response and server side handling.

[ https://issues.apache.org/jira/browse/KAFKA-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3307: -- Summary: Add ApiVersion request/response and server side handling. (was: Add ProtocolVersion

Re: Unknown licenses reported by './gradlew test'

Vahid, I rerun the same command on current trunk but do not reproduce this issue. I might be that you have some mis testing / util code in the folder, and although not added to the project, checkstyle still checks ALL files. Guozhang On Thu, Apr 21, 2016 at 11:05 AM, Vahid S Hashemian <

Unknown licenses reported by './gradlew test'

I have started getting this error when running './gradlew test': kafka@kafka:~/workspace/kafka$ ./gradlew test To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: https://docs.gradle.org/2.11/userguide/gradle_daemon.html. Building project 'core'

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252352#comment-15252352 ] Jiangjie Qin commented on KAFKA-3565: - [~jkreps] Yes, I agree that "free" calls can make a difference

[VOTE] KIP-56 Allow cross origin HTTP requests on all HTTP methods

Hi I would like to start vote on KIP-56. https://cwiki.apache.org/confluence/display/KAFKA/KIP-56%3A+Allow+cross+origin+HTTP+requests+on+all+HTTP+methods Thanks, -- Liquan Pei Software Engineer, Confluent Inc

[jira] [Commented] (KAFKA-3579) TopicCommand references outdated consumer property fetch.message.max.bytes

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

[GitHub] kafka pull request: KAFKA-3579 - Update reference to the outdated ...

Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1239 --- 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-3579) TopicCommand references outdated consumer property fetch.message.max.bytes

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

[GitHub] kafka pull request: KAFKA-3579 - Update reference to the outdated ...

GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1239 KAFKA-3579 - Update reference to the outdated consumer property Replace references to the old consumer property 'fetch.message.max.bytes' with the corresponding property in the new

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252152#comment-15252152 ] Jay Kreps commented on KAFKA-3565: -- Oh yeah, I think the critical question is what is the bottleneck? In

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252139#comment-15252139 ] Jay Kreps commented on KAFKA-3565: -- [~becket_qin] Yeah I think you are saying something like "previously

[jira] [Comment Edited] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252123#comment-15252123 ] Jiangjie Qin edited comment on KAFKA-3565 at 4/21/16 4:09 PM: -- [~jkreps] The

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252123#comment-15252123 ] Jiangjie Qin commented on KAFKA-3565: - [~jkreps] The google doc should be accessible now. I think

[jira] [Commented] (KAFKA-3594) Kafka new producer retries doesn't work in 0.9.0.1

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

[GitHub] kafka pull request: KAFKA-3594; After calling MemoryRecords.close(...

GitHub user omkreddy reopened a pull request: https://github.com/apache/kafka/pull/1249 KAFKA-3594; After calling MemoryRecords.close() method, hasRoomFor() method should return false This exception is occurring when producer is trying to append a record to a Re-enqueued record

[jira] [Commented] (KAFKA-3594) Kafka new producer retries doesn't work in 0.9.0.1

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

[GitHub] kafka pull request: KAFKA-3594; After calling MemoryRecords.close(...

Github user omkreddy closed the pull request at: https://github.com/apache/kafka/pull/1249 --- 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-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252069#comment-15252069 ] Jay Kreps commented on KAFKA-3565: -- [~ijuma] Yeah your data eliminates my guess. If the problem were the

[jira] [Updated] (KAFKA-3128) Add metrics for ZooKeeper events

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

[jira] [Assigned] (KAFKA-3128) Add metrics for ZooKeeper events

[ https://issues.apache.org/jira/browse/KAFKA-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3128: -- Assignee: Ismael Juma > Add metrics for ZooKeeper events > >

Kafka Streams - read topic from beginning

Kafka Streams look great, but there is one thing I don't seem to find a way to do: - read a topic from beginning even if there is a offset saved: I have : props.put(StreamsConfig.AUTO_OFFSET_RESET_CONFIG, "earliest"); this works as described if there is no offset

[jira] [Commented] (KAFKA-3599) Minor code cleanup

[ https://issues.apache.org/jira/browse/KAFKA-3599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15251933#comment-15251933 ] Matthias J. Sax commented on KAFKA-3599: [~guozhang] if I understand correctly, we remove

[jira] [Work started] (KAFKA-3599) Minor code cleanup

[ https://issues.apache.org/jira/browse/KAFKA-3599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3599 started by Matthias J. Sax. -- > Minor code cleanup > -- > > Key:

[jira] [Created] (KAFKA-3599) Minor code cleanup

Matthias J. Sax created KAFKA-3599: -- Summary: Minor code cleanup Key: KAFKA-3599 URL: https://issues.apache.org/jira/browse/KAFKA-3599 Project: Kafka Issue Type: Sub-task

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

[ https://issues.apache.org/jira/browse/KAFKA-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3598 started by Matthias J. Sax. -- > Improve JavaDoc of public API > - > >

[GitHub] kafka pull request: KAFKA-3598: Improve JavaDoc of public API

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/1250 KAFKA-3598: Improve JavaDoc of public API You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka JavaDoc-publicAPI Alternatively you can

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

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

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

[ https://issues.apache.org/jira/browse/KAFKA-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3598: --- Description: Add missing JavaDoc to all {{public}} methods of public API. Is related to

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

Matthias J. Sax created KAFKA-3598: -- Summary: Improve JavaDoc of public API Key: KAFKA-3598 URL: https://issues.apache.org/jira/browse/KAFKA-3598 Project: Kafka Issue Type: Sub-task

[jira] [Updated] (KAFKA-3568) KafkaProducer fails with timeout on message send()

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

[jira] [Updated] (KAFKA-3594) Kafka new producer retries doesn't work in 0.9.0.1

[ https://issues.apache.org/jira/browse/KAFKA-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-3594: --- Status: Patch Available (was: Open) > Kafka new producer retries doesn't work in 0.9.0.1 >

[GitHub] kafka pull request: KAFKA-3594; After calling MemoryRecords.close(...

GitHub user omkreddy opened a pull request: https://github.com/apache/kafka/pull/1249 KAFKA-3594; After calling MemoryRecords.close() method, hasRooFor() method should return false This exception is occurring when producer is trying to append a record to a Re-enqueued record batch

[jira] [Commented] (KAFKA-3594) Kafka new producer retries doesn't work in 0.9.0.1

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

[jira] [Comment Edited] (KAFKA-3594) Kafka new producer retries doesn't work in 0.9.0.1

[ https://issues.apache.org/jira/browse/KAFKA-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15251692#comment-15251692 ] Manikumar Reddy edited comment on KAFKA-3594 at 4/21/16 10:43 AM: -- Thanks

[jira] [Updated] (KAFKA-3594) Kafka new producer retries doesn't work in 0.9.0.1

[ https://issues.apache.org/jira/browse/KAFKA-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-3594: --- Assignee: Manikumar Reddy (was: Jun Rao) Priority: Critical (was: Major)

[jira] [Commented] (KAFKA-3589) KTable.count(final KeyValueMapper<K, V, K1> selector, String name) throw NPE

[ https://issues.apache.org/jira/browse/KAFKA-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15251533#comment-15251533 ] Damian Guy commented on KAFKA-3589: --- LGTM > KTable.count(final KeyValueMapper selector,

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15251422#comment-15251422 ] Jiangjie Qin commented on KAFKA-3565: - [~ijuma] [~junrao] [~jkreps] I just finished the parameterized