You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Alan Lau (Jira)" <ji...@apache.org> on 2026/08/11 19:50:00 UTC
[jira] [Assigned] (KAFKA-20518) Allow configuring a default StreamPartitioner
[ https://issues.apache.org/jira/browse/KAFKA-20518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Lau reassigned KAFKA-20518:
--------------------------------
Assignee: Alan Lau
> Allow configuring a default StreamPartitioner
> ---------------------------------------------
>
> Key: KAFKA-20518
> URL: https://issues.apache.org/jira/browse/KAFKA-20518
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Stef Noten
> Assignee: Alan Lau
> Priority: Minor
>
> Similar to configuring the default {{{}Serde{}}}s, it would be useful to be able to configure a default {{{}StreamPartitioner{}}}.
> Often, you want to treat certain keys always in the same manner. Currently such a decision translates into configuration of the partitioner on every possible operation, e.g. with foreign-key joins or groupings. Moreover, many automatic repartitions are subtly triggered downstream by making a small change upstream (e.g. changing {{processValues}} to a {{{}process{}}}). It's easy to make mistakes against this, especially as it's also not possible to verify partitioning with {{TopologyTestDriver}} nor with validations on the {{{}TopologyDescription{}}}.
> An example: in our application we have many composite record keys, which should always be partitioned by the first part. With a default partitioner, it would be possible to do automatic correct partitioning by e.g. key class type, annotation, implementing an interface, ...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)