[ 
https://issues.apache.org/jira/browse/KAFKA-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16110849#comment-16110849
 ] 

Paolo Patierno edited comment on KAFKA-5684 at 8/2/17 2:17 PM:
---------------------------------------------------------------

Maybe I made a mistake here because the default serdes are available only from 
the {{ProcessorContext}} (using the Streams configuration). The same is for the 
topic which is needed for deserialization. So in any case the checks for a) and 
b) are something that should happen inside the processor node at runtime during 
the flow. 
My first idea was creating a mapper (if one is not provided) with the right 
serdes (from parameters or default) upfront and passing it to the processor 
node creation doing the deserialization inside such mapper. 


was (Author: ppatierno):
Maybe I made a mistake here because the default serdes are available only from 
the {{ProcessorContext}} (using the Streams configuration). The same is for the 
topic which is needed for deserialization. So in any case the checks for a) and 
b) are something that should happen inside the processor node.

> KStreamPrintProcessor as customized KStreamPeekProcessor
> --------------------------------------------------------
>
>                 Key: KAFKA-5684
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5684
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Paolo Patierno
>            Assignee: Paolo Patierno
>            Priority: Minor
>
> Hi,
> the {{KStreamPrintProcessor}} is implemented from scratch (from the 
> {{AbstractProcessor}}) and the same for the related supplier.
> It looks to me that it's just a special {{KStreamPeekProcessor}} with 
> forwardDownStream to false and that allows the possibility to specify Serdes 
> instances used if key/values are bytes.
> At same time used by a {{print()}} method it provides a fast way to print 
> data flowing through the pipeline (while using just {{peek()}} you need to 
> write the code).
> I think that it could be useful to refactoring the {{KStreamPrintProcessor}} 
> as derived from the {{KStreamPeekProcessor}} customizing its behavior.
> Thanks,
> Paolo.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to