[jira] [Updated] (KAFKA-15282) Implement client support for KIP-848 client-side assignors
[ https://issues.apache.org/jira/browse/KAFKA-15282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk True updated KAFKA-15282: -- Fix Version/s: 4.0.0 > Implement client support for KIP-848 client-side assignors > -- > > Key: KAFKA-15282 > URL: https://issues.apache.org/jira/browse/KAFKA-15282 > Project: Kafka > Issue Type: New Feature > Components: clients, consumer >Reporter: Kirk True >Priority: Major > Labels: kip-848-client-support > Fix For: 4.0.0 > > > The client-side assignor provides the logic for the partition assignments > instead of on the server. Client-side assignment is the main approach used by > the “old protocol” for divvying up partitions. While the “new protocol” > favors server-side assignors, the client-side assignor will continue to be > used for backward compatibility, including KSQL, Connect, etc. > Note: I _*think*_ that the client-side assignor logic and the reconciliation > logic can remain separate from each other. We should strive to keep the two > pieces unencumbered, unless it’s unavoidable. > This task includes: > * Validate the client’s configuration for assignor selection > * Integrate with the new {{PartitionAssignor}} interface to invoke the logic > from the user-provided assignor implementation > * Implement the necessary logic around the request/response from the > {{ConsumerGroupPrepareAssignment}} RPC call using the information from the > {{PartitionAssignor}} above > * Implement the necessary logic around the request/response from the > {{ConsumerGroupInstallAssignment}} RPC call, again using the information > calculated by the {{PartitionAssignor}} > This task is part of the work to implement support for the new KIP-848 > consumer group protocol. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15282) Implement client support for KIP-848 client-side assignors
[ https://issues.apache.org/jira/browse/KAFKA-15282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk True updated KAFKA-15282: -- Fix Version/s: (was: 4.0.0) > Implement client support for KIP-848 client-side assignors > -- > > Key: KAFKA-15282 > URL: https://issues.apache.org/jira/browse/KAFKA-15282 > Project: Kafka > Issue Type: New Feature > Components: clients, consumer >Reporter: Kirk True >Priority: Major > Labels: kip-848-client-support > > The client-side assignor provides the logic for the partition assignments > instead of on the server. Client-side assignment is the main approach used by > the “old protocol” for divvying up partitions. While the “new protocol” > favors server-side assignors, the client-side assignor will continue to be > used for backward compatibility, including KSQL, Connect, etc. > Note: I _*think*_ that the client-side assignor logic and the reconciliation > logic can remain separate from each other. We should strive to keep the two > pieces unencumbered, unless it’s unavoidable. > This task includes: > * Validate the client’s configuration for assignor selection > * Integrate with the new {{PartitionAssignor}} interface to invoke the logic > from the user-provided assignor implementation > * Implement the necessary logic around the request/response from the > {{ConsumerGroupPrepareAssignment}} RPC call using the information from the > {{PartitionAssignor}} above > * Implement the necessary logic around the request/response from the > {{ConsumerGroupInstallAssignment}} RPC call, again using the information > calculated by the {{PartitionAssignor}} > This task is part of the work to implement support for the new KIP-848 > consumer group protocol. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15282) Implement client support for KIP-848 client-side assignors
[ https://issues.apache.org/jira/browse/KAFKA-15282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk True updated KAFKA-15282: -- Labels: kip-848-client-support (was: kip-848 kip-848-client-support) > Implement client support for KIP-848 client-side assignors > -- > > Key: KAFKA-15282 > URL: https://issues.apache.org/jira/browse/KAFKA-15282 > Project: Kafka > Issue Type: New Feature > Components: clients, consumer >Reporter: Kirk True >Priority: Major > Labels: kip-848-client-support > Fix For: 4.0.0 > > > The client-side assignor provides the logic for the partition assignments > instead of on the server. Client-side assignment is the main approach used by > the “old protocol” for divvying up partitions. While the “new protocol” > favors server-side assignors, the client-side assignor will continue to be > used for backward compatibility, including KSQL, Connect, etc. > Note: I _*think*_ that the client-side assignor logic and the reconciliation > logic can remain separate from each other. We should strive to keep the two > pieces unencumbered, unless it’s unavoidable. > This task includes: > * Validate the client’s configuration for assignor selection > * Integrate with the new {{PartitionAssignor}} interface to invoke the logic > from the user-provided assignor implementation > * Implement the necessary logic around the request/response from the > {{ConsumerGroupPrepareAssignment}} RPC call using the information from the > {{PartitionAssignor}} above > * Implement the necessary logic around the request/response from the > {{ConsumerGroupInstallAssignment}} RPC call, again using the information > calculated by the {{PartitionAssignor}} > This task is part of the work to implement support for the new KIP-848 > consumer group protocol. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15282) Implement client support for KIP-848 client-side assignors
[ https://issues.apache.org/jira/browse/KAFKA-15282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk True updated KAFKA-15282: -- Fix Version/s: 4.0.0 (was: 3.8.0) > Implement client support for KIP-848 client-side assignors > -- > > Key: KAFKA-15282 > URL: https://issues.apache.org/jira/browse/KAFKA-15282 > Project: Kafka > Issue Type: New Feature > Components: clients, consumer >Reporter: Kirk True >Priority: Major > Labels: kip-848, kip-848-client-support > Fix For: 4.0.0 > > > The client-side assignor provides the logic for the partition assignments > instead of on the server. Client-side assignment is the main approach used by > the “old protocol” for divvying up partitions. While the “new protocol” > favors server-side assignors, the client-side assignor will continue to be > used for backward compatibility, including KSQL, Connect, etc. > Note: I _*think*_ that the client-side assignor logic and the reconciliation > logic can remain separate from each other. We should strive to keep the two > pieces unencumbered, unless it’s unavoidable. > This task includes: > * Validate the client’s configuration for assignor selection > * Integrate with the new {{PartitionAssignor}} interface to invoke the logic > from the user-provided assignor implementation > * Implement the necessary logic around the request/response from the > {{ConsumerGroupPrepareAssignment}} RPC call using the information from the > {{PartitionAssignor}} above > * Implement the necessary logic around the request/response from the > {{ConsumerGroupInstallAssignment}} RPC call, again using the information > calculated by the {{PartitionAssignor}} > This task is part of the work to implement support for the new KIP-848 > consumer group protocol. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15282) Implement client support for KIP-848 client-side assignors
[ https://issues.apache.org/jira/browse/KAFKA-15282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk True updated KAFKA-15282: -- Parent: (was: KAFKA-14048) Issue Type: New Feature (was: Sub-task) > Implement client support for KIP-848 client-side assignors > -- > > Key: KAFKA-15282 > URL: https://issues.apache.org/jira/browse/KAFKA-15282 > Project: Kafka > Issue Type: New Feature > Components: clients, consumer >Reporter: Kirk True >Priority: Major > Labels: kip-848, kip-848-client-support > Fix For: 3.8.0 > > > The client-side assignor provides the logic for the partition assignments > instead of on the server. Client-side assignment is the main approach used by > the “old protocol” for divvying up partitions. While the “new protocol” > favors server-side assignors, the client-side assignor will continue to be > used for backward compatibility, including KSQL, Connect, etc. > Note: I _*think*_ that the client-side assignor logic and the reconciliation > logic can remain separate from each other. We should strive to keep the two > pieces unencumbered, unless it’s unavoidable. > This task includes: > * Validate the client’s configuration for assignor selection > * Integrate with the new {{PartitionAssignor}} interface to invoke the logic > from the user-provided assignor implementation > * Implement the necessary logic around the request/response from the > {{ConsumerGroupPrepareAssignment}} RPC call using the information from the > {{PartitionAssignor}} above > * Implement the necessary logic around the request/response from the > {{ConsumerGroupInstallAssignment}} RPC call, again using the information > calculated by the {{PartitionAssignor}} > This task is part of the work to implement support for the new KIP-848 > consumer group protocol. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15282) Implement client support for KIP-848 client-side assignors
[ https://issues.apache.org/jira/browse/KAFKA-15282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk True updated KAFKA-15282: -- Fix Version/s: 3.8.0 > Implement client support for KIP-848 client-side assignors > -- > > Key: KAFKA-15282 > URL: https://issues.apache.org/jira/browse/KAFKA-15282 > Project: Kafka > Issue Type: Sub-task > Components: clients, consumer >Reporter: Kirk True >Priority: Major > Labels: kip-848, kip-848-client-support > Fix For: 3.8.0 > > > The client-side assignor provides the logic for the partition assignments > instead of on the server. Client-side assignment is the main approach used by > the “old protocol” for divvying up partitions. While the “new protocol” > favors server-side assignors, the client-side assignor will continue to be > used for backward compatibility, including KSQL, Connect, etc. > Note: I _*think*_ that the client-side assignor logic and the reconciliation > logic can remain separate from each other. We should strive to keep the two > pieces unencumbered, unless it’s unavoidable. > This task includes: > * Validate the client’s configuration for assignor selection > * Integrate with the new {{PartitionAssignor}} interface to invoke the logic > from the user-provided assignor implementation > * Implement the necessary logic around the request/response from the > {{ConsumerGroupPrepareAssignment}} RPC call using the information from the > {{PartitionAssignor}} above > * Implement the necessary logic around the request/response from the > {{ConsumerGroupInstallAssignment}} RPC call, again using the information > calculated by the {{PartitionAssignor}} > This task is part of the work to implement support for the new KIP-848 > consumer group protocol. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15282) Implement client support for KIP-848 client-side assignors
[ https://issues.apache.org/jira/browse/KAFKA-15282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk True updated KAFKA-15282: -- Labels: kip-848 kip-848-client-support (was: consumer-threading-refactor kip-848 kip-848-client-support) > Implement client support for KIP-848 client-side assignors > -- > > Key: KAFKA-15282 > URL: https://issues.apache.org/jira/browse/KAFKA-15282 > Project: Kafka > Issue Type: Sub-task > Components: clients, consumer >Reporter: Kirk True >Priority: Major > Labels: kip-848, kip-848-client-support > > The client-side assignor provides the logic for the partition assignments > instead of on the server. Client-side assignment is the main approach used by > the “old protocol” for divvying up partitions. While the “new protocol” > favors server-side assignors, the client-side assignor will continue to be > used for backward compatibility, including KSQL, Connect, etc. > Note: I _*think*_ that the client-side assignor logic and the reconciliation > logic can remain separate from each other. We should strive to keep the two > pieces unencumbered, unless it’s unavoidable. > This task includes: > * Validate the client’s configuration for assignor selection > * Integrate with the new {{PartitionAssignor}} interface to invoke the logic > from the user-provided assignor implementation > * Implement the necessary logic around the request/response from the > {{ConsumerGroupPrepareAssignment}} RPC call using the information from the > {{PartitionAssignor}} above > * Implement the necessary logic around the request/response from the > {{ConsumerGroupInstallAssignment}} RPC call, again using the information > calculated by the {{PartitionAssignor}} > This task is part of the work to implement support for the new KIP-848 > consumer group protocol. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15282) Implement client support for KIP-848 client-side assignors
[ https://issues.apache.org/jira/browse/KAFKA-15282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk True updated KAFKA-15282: -- Parent: KAFKA-14048 Issue Type: Sub-task (was: Task) > Implement client support for KIP-848 client-side assignors > -- > > Key: KAFKA-15282 > URL: https://issues.apache.org/jira/browse/KAFKA-15282 > Project: Kafka > Issue Type: Sub-task > Components: clients, consumer >Reporter: Kirk True >Priority: Major > Labels: consumer-threading-refactor, kip-848, > kip-848-client-support > > The client-side assignor provides the logic for the partition assignments > instead of on the server. Client-side assignment is the main approach used by > the “old protocol” for divvying up partitions. While the “new protocol” > favors server-side assignors, the client-side assignor will continue to be > used for backward compatibility, including KSQL, Connect, etc. > Note: I _*think*_ that the client-side assignor logic and the reconciliation > logic can remain separate from each other. We should strive to keep the two > pieces unencumbered, unless it’s unavoidable. > This task includes: > * Validate the client’s configuration for assignor selection > * Integrate with the new {{PartitionAssignor}} interface to invoke the logic > from the user-provided assignor implementation > * Implement the necessary logic around the request/response from the > {{ConsumerGroupPrepareAssignment}} RPC call using the information from the > {{PartitionAssignor}} above > * Implement the necessary logic around the request/response from the > {{ConsumerGroupInstallAssignment}} RPC call, again using the information > calculated by the {{PartitionAssignor}} > This task is part of the work to implement support for the new KIP-848 > consumer group protocol. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15282) Implement client support for KIP-848 client-side assignors
[ https://issues.apache.org/jira/browse/KAFKA-15282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk True updated KAFKA-15282: -- Description: The client-side assignor provides the logic for the partition assignments instead of on the server. Client-side assignment is the main approach used by the “old protocol” for divvying up partitions. While the “new protocol” favors server-side assignors, the client-side assignor will continue to be used for backward compatibility, including KSQL, Connect, etc. Note: I _*think*_ that the client-side assignor logic and the reconciliation logic can remain separate from each other. We should strive to keep the two pieces unencumbered, unless it’s unavoidable. This task includes: * Validate the client’s configuration for assignor selection * Integrate with the new {{PartitionAssignor}} interface to invoke the logic from the user-provided assignor implementation * Implement the necessary logic around the request/response from the {{ConsumerGroupPrepareAssignment}} RPC call using the information from the {{PartitionAssignor}} above * Implement the necessary logic around the request/response from the {{ConsumerGroupInstallAssignment}} RPC call, again using the information calculated by the {{PartitionAssignor}} This task is part of the work to implement support for the new KIP-848 consumer group protocol. was: The client-side assignor provides the logic for the partition assignments instead of on the server. Client-side assignment is the main approach used by the “old protocol” for divvying up partitions. While the “new protocol” favors server-side assignors, the client-side assignor will continue to be used for backward compatibility, including KSQL, Connect, etc. Note: I _*think*_ that the client-side assignor logic and the [reconciliation logic|https://issues.apache.org/jira/browse/KAFKA-15276] can remain separate from each other. We should strive to keep the two pieces unencumbered, unless it’s unavoidable. This task includes: * Validate the client’s configuration for assignor selection * Integrate with the new {{PartitionAssignor}} interface to invoke the logic from the user-provided assignor implementation * Implement the necessary logic around the request/response from the {{ConsumerGroupPrepareAssignment}} RPC call using the information from the PartitionAssignor above * Implement the necessary logic around the request/response from the {{ConsumerGroupInstallAssignment}} RPC call, again using the information calculated by the {{PartitionAssignor}} This task is part of the work to implement support for the new KIP-848 consumer group protocol. > Implement client support for KIP-848 client-side assignors > -- > > Key: KAFKA-15282 > URL: https://issues.apache.org/jira/browse/KAFKA-15282 > Project: Kafka > Issue Type: Task > Components: clients, consumer >Reporter: Kirk True >Assignee: Kirk True >Priority: Major > Labels: consumer-threading-refactor, kip-848, > kip-848-client-support > > The client-side assignor provides the logic for the partition assignments > instead of on the server. Client-side assignment is the main approach used by > the “old protocol” for divvying up partitions. While the “new protocol” > favors server-side assignors, the client-side assignor will continue to be > used for backward compatibility, including KSQL, Connect, etc. > Note: I _*think*_ that the client-side assignor logic and the reconciliation > logic can remain separate from each other. We should strive to keep the two > pieces unencumbered, unless it’s unavoidable. > This task includes: > * Validate the client’s configuration for assignor selection > * Integrate with the new {{PartitionAssignor}} interface to invoke the logic > from the user-provided assignor implementation > * Implement the necessary logic around the request/response from the > {{ConsumerGroupPrepareAssignment}} RPC call using the information from the > {{PartitionAssignor}} above > * Implement the necessary logic around the request/response from the > {{ConsumerGroupInstallAssignment}} RPC call, again using the information > calculated by the {{PartitionAssignor}} > This task is part of the work to implement support for the new KIP-848 > consumer group protocol. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15282) Implement client support for KIP-848 client-side assignors
[ https://issues.apache.org/jira/browse/KAFKA-15282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk True updated KAFKA-15282: -- Description: The client-side assignor provides the logic for the partition assignments instead of on the server. Client-side assignment is the main approach used by the “old protocol” for divvying up partitions. While the “new protocol” favors server-side assignors, the client-side assignor will continue to be used for backward compatibility, including KSQL, Connect, etc. Note: I _*think*_ that the client-side assignor logic and the [reconciliation logic|https://issues.apache.org/jira/browse/KAFKA-15276] can remain separate from each other. We should strive to keep the two pieces unencumbered, unless it’s unavoidable. This task includes: * Validate the client’s configuration for assignor selection * Integrate with the new {{PartitionAssignor}} interface to invoke the logic from the user-provided assignor implementation * Implement the necessary logic around the request/response from the {{ConsumerGroupPrepareAssignment}} RPC call using the information from the PartitionAssignor above * Implement the necessary logic around the request/response from the {{ConsumerGroupInstallAssignment}} RPC call, again using the information calculated by the {{PartitionAssignor}} This task is part of the work to implement support for the new KIP-848 consumer group protocol. was: This includes: * Validate the client’s configuration for assignor selection * Validate the request/response from the {{ConsumerGroupHeartbeat}} RPC call This task is part of the work to implement support for the new KIP-848 consumer group protocol. > Implement client support for KIP-848 client-side assignors > -- > > Key: KAFKA-15282 > URL: https://issues.apache.org/jira/browse/KAFKA-15282 > Project: Kafka > Issue Type: Task > Components: clients, consumer >Reporter: Kirk True >Assignee: Kirk True >Priority: Major > Labels: consumer-threading-refactor, kip-848, > kip-848-client-support > > The client-side assignor provides the logic for the partition assignments > instead of on the server. Client-side assignment is the main approach used by > the “old protocol” for divvying up partitions. While the “new protocol” > favors server-side assignors, the client-side assignor will continue to be > used for backward compatibility, including KSQL, Connect, etc. > Note: I _*think*_ that the client-side assignor logic and the [reconciliation > logic|https://issues.apache.org/jira/browse/KAFKA-15276] can remain separate > from each other. We should strive to keep the two pieces unencumbered, unless > it’s unavoidable. > This task includes: > * Validate the client’s configuration for assignor selection > * Integrate with the new {{PartitionAssignor}} interface to invoke the logic > from the user-provided assignor implementation > * Implement the necessary logic around the request/response from the > {{ConsumerGroupPrepareAssignment}} RPC call using the information from the > PartitionAssignor above > * Implement the necessary logic around the request/response from the > {{ConsumerGroupInstallAssignment}} RPC call, again using the information > calculated by the {{PartitionAssignor}} > This task is part of the work to implement support for the new KIP-848 > consumer group protocol. -- This message was sent by Atlassian Jira (v8.20.10#820010)