[jira] [Commented] (TUBEMQ-312) Feedback more consumption information

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TUBEMQ-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176045#comment-17176045 ] 

ASF subversion and git services commented on TUBEMQ-312:
--------------------------------------------------------

Commit d2aef5ee8e943fc29c58c17f7bc748a60a13d1f8 in incubator-tubemq's branch refs/heads/master from gosonzhang
[ https://gitbox.apache.org/repos/asf?p=incubator-tubemq.git;h=d2aef5e ]

[TUBEMQ-312]Feedback more consumption information (#235)

Co-authored-by: gosonzhang <go...@tencent.com>

> Feedback more consumption information
> -------------------------------------
>
>                 Key: TUBEMQ-312
>                 URL: https://issues.apache.org/jira/browse/TUBEMQ-312
>             Project: Apache TubeMQ
>          Issue Type: Improvement
>          Components: Client, Server
>            Reporter: Guocheng Zhang
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Similar to TUBEMQ-311, when the consumer pulls the message, if the information status of the current partition can be fed back to the client, the processing on the consumer side will be more convenient, such as the maximum offset of the current consumed partition and the maximum data offset how much is it, what is the data offset of the current consumption location, etc. It will be very convenient if the business wants to do segmented consumption based on time period.



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