[
https://issues.apache.org/jira/browse/KAFKA-10448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
satya updated KAFKA-10448:
--------------------------
Description: Currently Kafka streams Sink Nodes use default partitioner or
has the provision of using a custom partitioner which has to be dependent on
key/value. I am looking for an enhancement of Sink Node to ensure source
partition is preserved instead of deriving the partition again using key/value.
One of our use case has producers which have custom partitioners that we dont
have access to as it is a third-party application. By simply preserving the
partition through context.partition() would be helpful. (was: Currently Kafka
streams Sink Nodes use default partitioner or has the provision of using a
custom partitioner which has to be dependent on key/value. I am looking for an
enhancement of Sink Node to ensure source partition is preserved instead of
deriving the partition again using key/value. One of our use case has producers
which have customer partitioners that we dont have access to as it is a
third-party application. By simply preserving the partition through
context.partition() would be helpful.)
> Preserve Source Partition in Kafka Streams from context
> -------------------------------------------------------
>
> Key: KAFKA-10448
> URL: https://issues.apache.org/jira/browse/KAFKA-10448
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Affects Versions: 2.5.0
> Reporter: satya
> Priority: Critical
>
> Currently Kafka streams Sink Nodes use default partitioner or has the
> provision of using a custom partitioner which has to be dependent on
> key/value. I am looking for an enhancement of Sink Node to ensure source
> partition is preserved instead of deriving the partition again using
> key/value. One of our use case has producers which have custom partitioners
> that we dont have access to as it is a third-party application. By simply
> preserving the partition through context.partition() would be helpful.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)