[
https://issues.apache.org/jira/browse/TUBEMQ-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174258#comment-17174258
]
Guocheng Zhang commented on TUBEMQ-311:
---------------------------------------
The main changes are as follows:
1. Add 3 parameters in SendMessageResponseB2P: messageId, appendTime,
appendOffset, respectively save the messageId of the message storage, the time
to save the message, and the index offset of the save message;
2. Adjust the generation method of messageId, which is globally unique by the
broker, and adjusted to be unique within the topic: messageId only needs to be
unique within the specified topic, reducing the conflict processing of data
generation;
3. Modify MessageSentResult and add 2 parameters appendTime and appendOffset
for the caller to use.
> Feedback more production information
> ------------------------------------
>
> Key: TUBEMQ-311
> URL: https://issues.apache.org/jira/browse/TUBEMQ-311
> Project: Apache TubeMQ
> Issue Type: Improvement
> Components: Client, Server
> Reporter: Guocheng Zhang
> Assignee: Guocheng Zhang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After the server successfully processes the Producer's message, if it can
> provide the producer with the storage time of the message and the starting
> offset position of the message storage, the business can better understand
> the production situation, such as the delay of the message from being sent to
> being accepted, the current storage location etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
