[
https://issues.apache.org/jira/browse/KAFKA-6958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Bejeck resolved KAFKA-6958.
--------------------------------
Resolution: Fixed
Thanks again [~fhussonnois] for your hard work and persistence in seeing this
valuable contribution through to completion!
> 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
> Assignee: Florian Hussonnois
> Priority: Minor
> Labels: kip
> Fix For: 2.4.0
>
>
> 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
(v8.3.4#803005)
