[jira] [Updated] (KAFKA-16256) Update ConsumerConfig to validate use of group.remote.assignor and partition.assignment.strategy based on group.protocol
[
https://issues.apache.org/jira/browse/KAFKA-16256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe updated KAFKA-16256:
-
Fix Version/s: (was: 3.9.0)
Removing release version 3.9 for this duplicate JIRA since it is confusing
release.py
> Update ConsumerConfig to validate use of group.remote.assignor and
> partition.assignment.strategy based on group.protocol
>
>
> Key: KAFKA-16256
> URL: https://issues.apache.org/jira/browse/KAFKA-16256
> Project: Kafka
> Issue Type: Improvement
> Components: clients, config, consumer
>Affects Versions: 3.7.0
>Reporter: Kirk True
>Assignee: Kirk True
>Priority: Blocker
> Labels: consumer-threading-refactor, kip-848-client-support
>
> {{ConsumerConfig}} supports both the {{group.remote.assignor}} and
> {{partition.assignment.strategy}} configuration options. These, however,
> should not be used together; the former is applicable only when the
> {{group.protocol}} is set to {{consumer}} and the latter when the
> {{group.protocol}} is set to {{{}classic{}}}. We should emit a warning if the
> user specifies the incorrect configuration based on the value of
> {{{}group.protocol{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (KAFKA-16256) Update ConsumerConfig to validate use of group.remote.assignor and partition.assignment.strategy based on group.protocol
[
https://issues.apache.org/jira/browse/KAFKA-16256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk True updated KAFKA-16256:
--
Component/s: config
> Update ConsumerConfig to validate use of group.remote.assignor and
> partition.assignment.strategy based on group.protocol
>
>
> Key: KAFKA-16256
> URL: https://issues.apache.org/jira/browse/KAFKA-16256
> Project: Kafka
> Issue Type: Improvement
> Components: clients, config, consumer
>Affects Versions: 3.7.0
>Reporter: Kirk True
>Assignee: Kirk True
>Priority: Blocker
> Labels: consumer-threading-refactor, kip-848-client-support
> Fix For: 3.9.0
>
>
> {{ConsumerConfig}} supports both the {{group.remote.assignor}} and
> {{partition.assignment.strategy}} configuration options. These, however,
> should not be used together; the former is applicable only when the
> {{group.protocol}} is set to {{consumer}} and the latter when the
> {{group.protocol}} is set to {{{}classic{}}}. We should emit a warning if the
> user specifies the incorrect configuration based on the value of
> {{{}group.protocol{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (KAFKA-16256) Update ConsumerConfig to validate use of group.remote.assignor and partition.assignment.strategy based on group.protocol
[
https://issues.apache.org/jira/browse/KAFKA-16256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe updated KAFKA-16256:
-
Fix Version/s: 3.9.0
(was: 4.0.0)
> Update ConsumerConfig to validate use of group.remote.assignor and
> partition.assignment.strategy based on group.protocol
>
>
> Key: KAFKA-16256
> URL: https://issues.apache.org/jira/browse/KAFKA-16256
> Project: Kafka
> Issue Type: Improvement
> Components: clients, consumer
>Affects Versions: 3.7.0
>Reporter: Kirk True
>Assignee: Kirk True
>Priority: Blocker
> Labels: consumer-threading-refactor, kip-848-client-support
> Fix For: 3.9.0
>
>
> {{ConsumerConfig}} supports both the {{group.remote.assignor}} and
> {{partition.assignment.strategy}} configuration options. These, however,
> should not be used together; the former is applicable only when the
> {{group.protocol}} is set to {{consumer}} and the latter when the
> {{group.protocol}} is set to {{{}classic{}}}. We should emit a warning if the
> user specifies the incorrect configuration based on the value of
> {{{}group.protocol{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (KAFKA-16256) Update ConsumerConfig to validate use of group.remote.assignor and partition.assignment.strategy based on group.protocol
[
https://issues.apache.org/jira/browse/KAFKA-16256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk True updated KAFKA-16256:
--
Priority: Blocker (was: Minor)
> Update ConsumerConfig to validate use of group.remote.assignor and
> partition.assignment.strategy based on group.protocol
>
>
> Key: KAFKA-16256
> URL: https://issues.apache.org/jira/browse/KAFKA-16256
> Project: Kafka
> Issue Type: Improvement
> Components: clients, consumer
>Affects Versions: 3.7.0
>Reporter: Kirk True
>Assignee: Kirk True
>Priority: Blocker
> Labels: consumer-threading-refactor, kip-848-client-support
> Fix For: 4.0.0
>
>
> {{ConsumerConfig}} supports both the {{group.remote.assignor}} and
> {{partition.assignment.strategy}} configuration options. These, however,
> should not be used together; the former is applicable only when the
> {{group.protocol}} is set to {{consumer}} and the latter when the
> {{group.protocol}} is set to {{{}classic{}}}. We should emit a warning if the
> user specifies the incorrect configuration based on the value of
> {{{}group.protocol{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (KAFKA-16256) Update ConsumerConfig to validate use of group.remote.assignor and partition.assignment.strategy based on group.protocol
[
https://issues.apache.org/jira/browse/KAFKA-16256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk True updated KAFKA-16256:
--
Fix Version/s: 4.0.0
(was: 3.8.0)
> Update ConsumerConfig to validate use of group.remote.assignor and
> partition.assignment.strategy based on group.protocol
>
>
> Key: KAFKA-16256
> URL: https://issues.apache.org/jira/browse/KAFKA-16256
> Project: Kafka
> Issue Type: Improvement
> Components: clients, consumer
>Affects Versions: 3.7.0
>Reporter: Kirk True
>Assignee: Kirk True
>Priority: Minor
> Labels: consumer-threading-refactor, kip-848-client-support
> Fix For: 4.0.0
>
>
> {{ConsumerConfig}} supports both the {{group.remote.assignor}} and
> {{partition.assignment.strategy}} configuration options. These, however,
> should not be used together; the former is applicable only when the
> {{group.protocol}} is set to {{consumer}} and the latter when the
> {{group.protocol}} is set to {{{}classic{}}}. We should emit a warning if the
> user specifies the incorrect configuration based on the value of
> {{{}group.protocol{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (KAFKA-16256) Update ConsumerConfig to validate use of group.remote.assignor and partition.assignment.strategy based on group.protocol
[
https://issues.apache.org/jira/browse/KAFKA-16256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk True updated KAFKA-16256:
--
Priority: Minor (was: Major)
> Update ConsumerConfig to validate use of group.remote.assignor and
> partition.assignment.strategy based on group.protocol
>
>
> Key: KAFKA-16256
> URL: https://issues.apache.org/jira/browse/KAFKA-16256
> Project: Kafka
> Issue Type: Improvement
> Components: clients, consumer
>Affects Versions: 3.7.0
>Reporter: Kirk True
>Assignee: Kirk True
>Priority: Minor
> Labels: consumer-threading-refactor, kip-848-client-support
> Fix For: 3.8.0
>
>
> {{ConsumerConfig}} supports both the {{group.remote.assignor}} and
> {{partition.assignment.strategy}} configuration options. These, however,
> should not be used together; the former is applicable only when the
> {{group.protocol}} is set to {{consumer}} and the latter when the
> {{group.protocol}} is set to {{{}classic{}}}. We should emit a warning if the
> user specifies the incorrect configuration based on the value of
> {{{}group.protocol{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
