[
https://issues.apache.org/jira/browse/KAFKA-20155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18060526#comment-18060526
]
Matthias J. Sax commented on KAFKA-20155:
-----------------------------------------
{quote}We run into similar challenges in the changelogging layer
(https://issues.apache.org/jira/browse/KAFKA-20179)
{quote}
This is actually a good point – seems, as long as we don't resolve K20179, it
does also not make much sense to do lazy deserialization, as we would need to
pass the deserialized headers into the change-logger anyway...
> Implement lazy deserialization mechanism
> ----------------------------------------
>
> Key: KAFKA-20155
> URL: https://issues.apache.org/jira/browse/KAFKA-20155
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
> Reporter: TengYao Chi
> Assignee: TengYao Chi
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
