[
https://issues.apache.org/jira/browse/KAFKA-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606491#comment-15606491
]
Guozhang Wang commented on KAFKA-3455:
--------------------------------------
[~jonathan.bender] I'm looking at this JIRA again, and I'm wondering if it can
actually be done via the {{transform}} function. As you mentioned in the email
thread:
{code}
I was trying to build a topology using the DSL, add a custom processor and then
add a sink for it. However, it seems like there's no great way to do
this using the APIs, since the processor's internal "name" is not exposed in
the KStream interface, and the .process method doesn't return the latest
KStream.
{code}
We could potentially do {{stream.transform(...).to(...)}}.
> Connect custom processors with the streams DSL
> ----------------------------------------------
>
> Key: KAFKA-3455
> URL: https://issues.apache.org/jira/browse/KAFKA-3455
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
> Affects Versions: 0.10.0.1
> Reporter: Jonathan Bender
> Labels: user-experience
> Fix For: 0.10.2.0
>
>
> From the kafka users email thread, we discussed the idea of connecting custom
> processors with topologies defined from the Streams DSL (and being able to
> sink data from the processor). Possibly this could involve exposing the
> underlying processor's name in the streams DSL so it can be connected with
> the standard processor API.
> {quote}
> Thanks for the feedback. This is definitely something we wanted to support
> in the Streams DSL.
> One tricky thing, though, is that some operations do not translate to a
> single processor, but a sub-graph of processors (think of a stream-stream
> join, which is translated to actually 5 processors for windowing / state
> queries / merging, each with a different internal name). So how to define
> the API to return the processor name needs some more thinking.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
