Re: [VOTE]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

+1. Thanks! On Sat, Jul 8, 2017 at 1:35 AM, Damian Guy wrote: > +1 > On Fri, 7 Jul 2017 at 16:08, Eno Thereska wrote: > > > +1 (non-binding) Thanks. > > > > Eno > > > On 6 Jul 2017, at 21:49, Gwen Shapira wrote: > > > > > > +1 >

[jira] [Resolved] (KAFKA-5598) Make OffsetReader accessible in ConnectorContext

[ https://issues.apache.org/jira/browse/KAFKA-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Kuznetsov resolved KAFKA-5598. --- Resolution: Duplicate > Make OffsetReader accessible in ConnectorContext >

[jira] [Created] (KAFKA-5598) Make OffsetReader accessible in ConnectorContext

Oleg Kuznetsov created KAFKA-5598: - Summary: Make OffsetReader accessible in ConnectorContext Key: KAFKA-5598 URL: https://issues.apache.org/jira/browse/KAFKA-5598 Project: Kafka Issue Type:

[GitHub] kafka pull request #3530: KAFKA-5595: Ensure client connection ids are not r...

GitHub user rajinisivaram reopened a pull request: https://github.com/apache/kafka/pull/3530 KAFKA-5595: Ensure client connection ids are not reused too quickly When there are broker delays that cause a response to take longer than `connections.max.idle.ms`, connections may be

[GitHub] kafka pull request #3530: KAFKA-5595: Ensure client connection ids are not r...

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

Behavior when kafka producer is network partitioned

What is the behaviour in 0.10.x if kafka producer is not able to reach any of the broker for a brief duration? >From what I understand from the code, all the nodes will be in disconnected state. Since there is no node to query to, client will never query any node and update the cluster. Even if

Re: kafka connect

In case you do not find Kafka Connector for listening to TCP sockets, you can use NiFi for this task. NiFi has a processor to listen to TCP messages. On Tue, Jul 4, 2017 at 1:26 PM, Clay Teahouse wrote: > Hello All, > > I have a few questions regarding kafka connect. I'd

[GitHub] kafka pull request #3535: KAFKA-5597: Autogenerate producer sender metrics.

GitHub user wushujames opened a pull request: https://github.com/apache/kafka/pull/3535 KAFKA-5597: Autogenerate producer sender metrics. Subtask of https://issues.apache.org/jira/browse/KAFKA-3480 The changes are very similar to what was done for the consumer in

[jira] [Created] (KAFKA-5597) Autogenerate Producer sender metrics

James Cheng created KAFKA-5597: -- Summary: Autogenerate Producer sender metrics Key: KAFKA-5597 URL: https://issues.apache.org/jira/browse/KAFKA-5597 Project: Kafka Issue Type: Sub-task

[GitHub] kafka pull request #3478: KAFKA-3539: KafkaProducer.send() should not block

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