You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Konstantine Karantasis (Jira)" <ji...@apache.org> on 2021/07/09 20:42:00 UTC
[jira] [Commented] (KAFKA-10046) Deprecated PartitionGrouper config
is ignored
[ https://issues.apache.org/jira/browse/KAFKA-10046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17378294#comment-17378294 ]
Konstantine Karantasis commented on KAFKA-10046:
------------------------------------------------
[~ableegoldman] the two issues you mention above have been resolved. Thus, marking the issue here as resolved too and I assume it's completed for AK 3.0
> Deprecated PartitionGrouper config is ignored
> ---------------------------------------------
>
> Key: KAFKA-10046
> URL: https://issues.apache.org/jira/browse/KAFKA-10046
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: John Roesler
> Priority: Blocker
> Fix For: 3.0.0
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)