[jira] [Assigned] (KAFKA-2391) Blocking call such as position(), partitionsFor(), committed() and listTopics() should have a timeout

[ https://issues.apache.org/jira/browse/KAFKA-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat reassigned KAFKA-2391: -- Assignee: Mayuresh Gharat > Blocking call such as position(), partitionsFor(), committe

[jira] [Updated] (KAFKA-2387) Improve KafkaConsumer API

[ https://issues.apache.org/jira/browse/KAFKA-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-2387: Assignee: (was: Dong Lin) > Improve KafkaConsumer API > - > > Ke

[jira] [Assigned] (KAFKA-2388) subscribe(topic)/unsubscribe(topic) should either take a callback to allow user to handle exceptions or it should be synchronous.

[ https://issues.apache.org/jira/browse/KAFKA-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin reassigned KAFKA-2388: --- Assignee: Dong Lin > subscribe(topic)/unsubscribe(topic) should either take a callback to allow > us

[jira] [Assigned] (KAFKA-2390) Seek() should take a callback.

[ https://issues.apache.org/jira/browse/KAFKA-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin reassigned KAFKA-2390: --- Assignee: Dong Lin > Seek() should take a callback. > -- > >

[jira] [Assigned] (KAFKA-2387) Improve KafkaConsumer API

[ https://issues.apache.org/jira/browse/KAFKA-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin reassigned KAFKA-2387: --- Assignee: Dong Lin > Improve KafkaConsumer API > - > > Key: K

[jira] [Created] (KAFKA-2391) Blocking call such as position(), partitionsFor(), committed() and listTopics() should have a timeout

Jiangjie Qin created KAFKA-2391: --- Summary: Blocking call such as position(), partitionsFor(), committed() and listTopics() should have a timeout Key: KAFKA-2391 URL: https://issues.apache.org/jira/browse/KAFKA-2391

[jira] [Created] (KAFKA-2390) Seek() should take a callback.

Jiangjie Qin created KAFKA-2390: --- Summary: Seek() should take a callback. Key: KAFKA-2390 URL: https://issues.apache.org/jira/browse/KAFKA-2390 Project: Kafka Issue Type: Sub-task R

[jira] [Created] (KAFKA-2389) CommitType seems not necessary in commit().

Jiangjie Qin created KAFKA-2389: --- Summary: CommitType seems not necessary in commit(). Key: KAFKA-2389 URL: https://issues.apache.org/jira/browse/KAFKA-2389 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-2388) subscribe(topic)/unsubscribe(topic) should either take a callback to allow user to handle exceptions or it should be synchronous.

Jiangjie Qin created KAFKA-2388: --- Summary: subscribe(topic)/unsubscribe(topic) should either take a callback to allow user to handle exceptions or it should be synchronous. Key: KAFKA-2388 URL: https://issues.apache

[jira] [Created] (KAFKA-2387) Improve KafkaConsumer API

Jiangjie Qin created KAFKA-2387: --- Summary: Improve KafkaConsumer API Key: KAFKA-2387 URL: https://issues.apache.org/jira/browse/KAFKA-2387 Project: Kafka Issue Type: Improvement Rep

Re: Review Request 33620: Patch for KAFKA-1690

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/33620/#review93684 --- clients/src/main/java/org/apache/kafka/common/network/SSLTransportL

[jira] [Created] (KAFKA-2386) Transient test failure: testGenerationIdIncrementsOnRebalance

Jason Gustafson created KAFKA-2386: -- Summary: Transient test failure: testGenerationIdIncrementsOnRebalance Key: KAFKA-2386 URL: https://issues.apache.org/jira/browse/KAFKA-2386 Project: Kafka

Re: Review Request 33620: Patch for KAFKA-1690

> On July 30, 2015, 10:37 p.m., Dong Lin wrote: > > clients/src/main/java/org/apache/kafka/common/network/SSLTransportLayer.java, > > line 416 > > > > > > Do you mean unwrapResult.getHandshakeStatus() == > > Hands

[jira] [Commented] (KAFKA-2143) Replicas get ahead of leader and fail

[ https://issues.apache.org/jira/browse/KAFKA-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648444#comment-14648444 ] Rafael Bagmanov commented on KAFKA-2143: I would like to add that we are experienc

Re: Review Request 33620: Patch for KAFKA-1690

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/33620/#review93652 --- clients/src/main/java/org/apache/kafka/common/network/SSLTransportL

[jira] [Commented] (KAFKA-1387) Kafka getting stuck creating ephemeral node it has already created when two zookeeper sessions are established in a very short period of time

[ https://issues.apache.org/jira/browse/KAFKA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648378#comment-14648378 ] Clark Haskins commented on KAFKA-1387: -- This patch is listed as a blocker. Can the ex

Build failed in Jenkins: KafkaPreCommit #170

See Changes: [wangguoz] KAFKA-2350; KafkaConsumer pause/resume API [wangguoz] KAFKA-2026: fix logging of unsued options always showing null; reviewed by Ewen Cheslack-Postava and Jiangjie Qin --

Re: [DISCUSS] KIP-28 - Add a transform client for data processing

I agree with Sriram and Martin. Kafka is already about providing streams of data, and so Kafka Streams or anything like that is confusing to me. This new library is about making it easier to process the data. -James On Jul 30, 2015, at 9:38 AM, Aditya Auradkar wrote: > Personally, I prefer K

[jira] [Commented] (KAFKA-2026) Logging of unused options always shows null for the value and is misleading if the option is used by serializers

[ https://issues.apache.org/jira/browse/KAFKA-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648343#comment-14648343 ] Guozhang Wang commented on KAFKA-2026: -- Thanks. I agree the current warning message m

[jira] [Updated] (KAFKA-2026) Logging of unused options always shows null for the value and is misleading if the option is used by serializers

[ https://issues.apache.org/jira/browse/KAFKA-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2026: - Resolution: Fixed Status: Resolved (was: Patch Available) > Logging of unused options alw

[jira] [Updated] (KAFKA-2350) Add KafkaConsumer pause capability

[ https://issues.apache.org/jira/browse/KAFKA-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2350: - Fix Version/s: (was: 0.9.0) 0.8.3 > Add KafkaConsumer pause capability > --

[jira] [Resolved] (KAFKA-2350) Add KafkaConsumer pause capability

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

[jira] [Commented] (KAFKA-2350) Add KafkaConsumer pause capability

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

[GitHub] kafka pull request: KAFKA-2350; KafkaConsumer pause/resume API

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/100 --- 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-2026) Logging of unused options always shows null for the value and is misleading if the option is used by serializers

[ https://issues.apache.org/jira/browse/KAFKA-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648279#comment-14648279 ] Ewen Cheslack-Postava commented on KAFKA-2026: -- [~guozhang] This looks fine t

Re: Review Request 33620: Patch for KAFKA-1690

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/33620/#review93639 --- clients/src/main/java/org/apache/kafka/common/config/AbstractConfig

Re: Review Request 35421: Patch for KAFKA-2026

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35421/#review93636 --- Ship it! Ship It! - Ewen Cheslack-Postava On June 13, 2015, 10:0

[jira] [Updated] (KAFKA-2026) Logging of unused options always shows null for the value and is misleading if the option is used by serializers

[ https://issues.apache.org/jira/browse/KAFKA-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2026: - Reviewer: Ewen Cheslack-Postava > Logging of unused options always shows null for the value and is

[jira] [Commented] (KAFKA-2026) Logging of unused options always shows null for the value and is misleading if the option is used by serializers

[ https://issues.apache.org/jira/browse/KAFKA-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648201#comment-14648201 ] Guozhang Wang commented on KAFKA-2026: -- Assigning to [~ewencp] for reviews. > Loggin

Gauging Interest in adding Encryption to Kafka

Hi, Based on the security wiki page encryption of data at rest is out of scope for the time being. However, we are implementing encryption in Kafka and would like to see if there is interest in submitting a patch got it. I suppose tha

Re: Kafka Consumer thoughts

Hey Becket, Yeah the high-level belief here is that it is possible to give something as high level as the existing "high level" consumer, but this is not likely to be the end-all be-all of high-level interfaces for processing streams of messages. For example neither of these interfaces handles the

[jira] [Updated] (KAFKA-2385) zookeeper-shell does not work

[ https://issues.apache.org/jira/browse/KAFKA-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-2385: Fix Version/s: 0.8.3 > zookeeper-shell does not work > - > >

[jira] [Updated] (KAFKA-2385) zookeeper-shell does not work

[ https://issues.apache.org/jira/browse/KAFKA-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-2385: Component/s: tools > zookeeper-shell does not work > - > >

[jira] [Created] (KAFKA-2385) zookeeper-shell does not work

Jiangjie Qin created KAFKA-2385: --- Summary: zookeeper-shell does not work Key: KAFKA-2385 URL: https://issues.apache.org/jira/browse/KAFKA-2385 Project: Kafka Issue Type: Bug Reporte

Re: Review Request 36858: Patch for KAFKA-2120

> On July 27, 2015, 10:55 p.m., Jason Gustafson wrote: > > clients/src/main/java/org/apache/kafka/clients/ClientRequest.java, line 26 > > > > > > Should ClientResponse.requestLatencyMs be updated to use sendMs instead

Re: [DISCUSS] Reviewers in commit message

On Thu, Jul 30, 2015 at 6:04 PM, Gwen Shapira wrote: > I wasn't aware of this history, thanks for explaining! > No problem. :) In most Apache projects I contributed to, the list of things that are > stated in "reviewed by" are implied in a committer committing the > patch. Reviewers are there t

Re: [DISCUSS] Reviewers in commit message

I wasn't aware of this history, thanks for explaining! In most Apache projects I contributed to, the list of things that are stated in "reviewed by" are implied in a committer committing the patch. Reviewers are there to help the committer make the decision (thats why I sometimes mention "@ewencp

Re: [DISCUSS] KIP-28 - Add a transform client for data processing

Personally, I prefer KafkaStreams just because it sounds nicer. For the reasons identified above, KafkaProcessor or KProcessor is more apt but sounds less catchy (IMO). I also think we should prefix with Kafka (rather than K) because we will then have 3 clients: KafkaProducer, KafkaConsumer and Kaf

[jira] [Updated] (KAFKA-2120) Add a request timeout to NetworkClient

[ https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat updated KAFKA-2120: --- Fix Version/s: 0.8.3 > Add a request timeout to NetworkClient > --

Re: [DISCUSS] KIP-28 - Add a transform client for data processing

I think its also a matter of intent. If we see it as "yet another client library", than Processor (to match Producer and Consumer) will work great. If we see it is a stream processing framework, the name has to start with S to follow existing convention. Speaking of naming conventions: You know ho

ReplicaManager recover after losing a broker

We run 5 node kafka cluster in production with replication factor is 3. If we lose a broker for couple days and kafka-data is wiped off when it comes back online, we had to do rolling restart of all brokers to make them heathy. It recovers itself for most part, FailedFetchRequests and UnderReplica

New Consumer API and Range Consumption with Fail-over

Hello Kafka Dev Team, With new Consumer API redesign ( https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/consumer/KafkaConsumer.java ), is there a capability to consume given the topic and partition start/ end position. How would I achieve following use

Re: Review Request 28096: Patch for KAFKA-313

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/28096/#review93559 --- core/src/main/scala/kafka/admin/ConsumerGroupCommand.scala (line 45

[jira] [Commented] (KAFKA-2120) Add a request timeout to NetworkClient

[ https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647423#comment-14647423 ] Stevo Slavic commented on KAFKA-2120: - If this is considered as must have for Kafka 0.

Re: [DISCUSS] KIP-28 - Add a transform client for data processing

I had the same thought. Kafka processor, KProcessor or even Kafka stream processor is more relevant. > On Jul 30, 2015, at 2:09 PM, Martin Kleppmann wrote: > > I'm with Sriram -- Kafka is all about streams already (or topics, to be > precise, but we're calling it "stream processing" not "topic

Re: [DISCUSS] KIP-28 - Add a transform client for data processing

I'm with Sriram -- Kafka is all about streams already (or topics, to be precise, but we're calling it "stream processing" not "topic processing"), so I find "Kafka Streams", "KStream" and "Kafka Streaming" all confusing, since they seem to imply that other bits of Kafka are not about streams. I

Re: [DISCUSS] KIP-28 - Add a transform client for data processing

I would vote for KStream as it sounds sexier (is it only me??), second to that would be Kafka Streaming. On Wed, Jul 29, 2015 at 6:08 PM, Jay Kreps wrote: > Also, the most important part of any prototype, we should have a name for > this producing-consumer-thingamgigy: > > Various ideas: > - Kaf