[
https://issues.apache.org/jira/browse/KAFKA-21009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18113137#comment-18113137
]
Matthias J. Sax commented on KAFKA-21009:
-----------------------------------------
{quote}Are you planning to work on a KIP for the callback-based approach?
{quote}
I won't have capacity to work on this. Note, there was also a comment on the
other ticket, if it can get picked up. I left a comment there. Same applies
here.
But the main thing would be, that you and [~hrbaskaran] sync up to avoid
duplicate work (we have also seen folks to collaborate on KIPs in the past, so
if you are both open to it, you could also work together).
> Consider introducing record header handling policies for Kafka Streams
> stateful operations
> ------------------------------------------------------------------------------------------
>
> Key: KAFKA-21009
> URL: https://issues.apache.org/jira/browse/KAFKA-21009
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: sanghyeok An
> Assignee: sanghyeok An
> Priority: Minor
> Labels: needs-kip
>
> Stateful operations such as joins and aggregations may combine or retain
> records from multiple inputs. Unlike one-to-one stateless operations, there
> may not be an obvious set of headers to use for the output record.
>
> Currently, header handling is determined by the behavior of each operator,
> and applications do not have an explicit policy for controlling it.
>
> We should consider whether Kafka Streams stateful operations could support
> header handling policies such as:
> * Retaining the existing behavior
> * Ignoring or dropping headers
> * Preserving headers from a selected input record
> * Merging headers from multiple input records
> This Jira is intended to capture the use case and evaluate whether such
> policies would be useful. If pursued, the affected operators, exact policy
> set, defaults, conflict handling, and consistency across caching and
> restoration should be defined through a KIP.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
