Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
2.6.0
-
None
-
None
Description
It looks like at some point, we accidentally broke the chain that lets the user-provided PartitionGrouper config actually get to the Consumer-managed StreamsPartitionAssignor. The effect is that any configured value would just be ignored.
Investigation is needed to determine when this regression took place and whether we should fix it or just remove the config.
See the discussion in https://github.com/apache/kafka/pull/8716/ . The TaskAssignorIntegrationTest in that PR can be used to verify this regression.
Attachments
Issue Links
- relates to
-
KAFKA-7785 Remove PartitionGrouper interface and it's config and move DefaultPartitionGrouper to internal package
- Resolved
-
KAFKA-4117 Cleanup StreamPartitionAssignor behavior
- Resolved
-
KAFKA-8927 Remove config `partition.grouper` and interface `PartitionGrouper`
- Resolved