You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tubemq.apache.org by "Guocheng Zhang (Jira)" <ji...@apache.org> on 2020/05/14 11:48:00 UTC

[jira] [Updated] (TUBEMQ-113) Improve the consumption control ability of the client

     [ https://issues.apache.org/jira/browse/TUBEMQ-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guocheng Zhang updated TUBEMQ-113:
----------------------------------
    Description: 
Similar to Kafka, the relationship between partitions and consumers is specified and managed by the clients, rather than only one solution that is now completely distributed and managed by the server

1. Consumer allocation and management partition: Consumers can specify which partition to be consumed and where the consumption offset starts and ends. The entire consumer group can consume only part of the partition data such that the server is not responsible for the allocation.

2. The system must provide relevant offset information when production and consumption are successful, and the system also needs to support the client to query various metadata

  was:
Similar to Kafka, the relationship between partitions and consumers is specified and managed by the clients, rather than only one solution that is now completely distributed and managed by the server

1. Consumer allocation and management partition: Consumers can specify the partition to be used, where the consumption offset starts and ends; at the same time, the entire consumer group can only consume part of the partition data; the server is not responsible for the partition allocation of this type of consumer group

2. The system must provide relevant offset information when production and consumption are successful, and the system also needs to support the client to query various metadata


> Improve the consumption control ability of the client
> -----------------------------------------------------
>
>                 Key: TUBEMQ-113
>                 URL: https://issues.apache.org/jira/browse/TUBEMQ-113
>             Project: Apache TubeMQ
>          Issue Type: Task
>            Reporter: Guocheng Zhang
>            Priority: Major
>              Labels: features
>
> Similar to Kafka, the relationship between partitions and consumers is specified and managed by the clients, rather than only one solution that is now completely distributed and managed by the server
> 1. Consumer allocation and management partition: Consumers can specify which partition to be consumed and where the consumption offset starts and ends. The entire consumer group can consume only part of the partition data such that the server is not responsible for the allocation.
> 2. The system must provide relevant offset information when production and consumption are successful, and the system also needs to support the client to query various metadata



--
This message was sent by Atlassian Jira
(v8.3.4#803005)