Please, give me permission to create a KIP in Kafka

[Flávio Stutz]

Hi.
I want to propose a KIP and need access to do it.
Please give me access if possible.

The initial discussion of the KIP can be seen here:
https://issues.apache.org/jira/browse/KAFKA-6953

Thanks.

Flávio Stutz

Re: [VOTE] KIP-264: Add a consumer metric to record raw fetch size

[Ted Yu]

lgtm

On Fri, May 25, 2018 at 10:51 AM, Vahid S Hashemian <
vahidhashem...@us.ibm.com> wrote:

> In the absence of additional feedback on this KIP I'd like to start a
> vote.
>
> To summarize, the KIP simply proposes to add a consumer metric to track
> the size of raw (uncompressed) fetched messages.
> The KIP can be found here:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-
> 264%3A+Add+a+consumer+metric+to+record+raw+fetch+size
>
> Thanks.
> --Vahid
>
>
>

Re: Load testing Apche kafka usimh jmeter

[Ted Yu]

Have you seen this ?

https://dzone.com/articles/apache-kafka-how-to-load-test-with-jmeter

There is also:

https://github.com/BrightTag/kafkameter

On Fri, May 25, 2018 at 1:36 AM, Vihar Nani 
wrote:

> Hi Team,
>
> Can anyone help me with steps of integrating Apche kafa with Apche Jmeter?
>
> I have been trying to load testing Kafka with Jmeter, But I couldn't get
> proper information on this.
>
>
>
>
>
>
>
> Thanks,
> ~Vihar Gangineni
>

[DISCUSS] KIP-307: Allow to define custom processor names with KStreams DSL

[Florian Hussonnois]

Hi,

I would like to start a new discussion on following KIP :
https://cwiki.apache.org/confluence/display/KAFKA/KIP-307%3A+Allow+to+define+custom+processor+names+with+KStreams+DSL

This is still a draft.

Looking forward for your feedback.
-- 
Florian HUSSONNOIS

[jira] [Created] (KAFKA-6958) Allow to define custom processor names with KStreams DSL

[Florian Hussonnois (JIRA)]

Florian Hussonnois created KAFKA-6958:
-

 Summary: Allow to define custom processor names with KStreams DSL
 Key: KAFKA-6958
 URL: https://issues.apache.org/jira/browse/KAFKA-6958
 Project: Kafka
  Issue Type: Improvement
  Components: streams
Affects Versions: 1.1.0
Reporter: Florian Hussonnois


Currently, while building a new Topology through the KStreams DSL the 
processors are automatically named.

The genarated names are prefixed depending of the operation (i.e 
KSTREAM-SOURCE, KSTREAM-FILTER, KSTREAM-MAP, etc).

To debug/understand a topology it is possible to display the processor lineage 
with the method Topology#describe(). However, a complex topology with dozens of 
operations can be hard to understand if the processor names are not relevant.

It would be useful to be able to set more meaningful names. For example, a 
processor name could describe the business rule performed by a map() operation.

[KIP-307|https://cwiki.apache.org/confluence/display/KAFKA/KIP-307%3A+Allow+to+define+custom+processor+names+with+KStreams+DSL]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Jenkins build is back to normal : kafka-trunk-jdk10 #142

[Apache Jenkins Server]

See 

[jira] [Resolved] (KAFKA-6956) Use Java AdminClient in BrokerApiVersionsCommand

[Vahid Hashemian (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vahid Hashemian resolved KAFKA-6956.

Resolution: Duplicate

> Use Java AdminClient in BrokerApiVersionsCommand
> 
>
> Key: KAFKA-6956
> URL: https://issues.apache.org/jira/browse/KAFKA-6956
> Project: Kafka
>  Issue Type: Improvement
>Reporter: Ismael Juma
>Assignee: Vahid Hashemian
>Priority: Major
>
> The Scala AdminClient was introduced as a stop gap until we had an officially 
> supported API. The Java AdminClient is the supported API so we should migrate 
> all usages to it and remove the Scala AdminClient. This JIRA is for using the 
> Java AdminClient in BrokerApiVersionsCommand. We would need to verify that 
> the necessary APIs are available via the Java AdminClient.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)