drpmma opened a new issue, #7543:
URL: https://github.com/apache/rocketmq/issues/7543

   ### Before Creating the Enhancement Request
   
   - [X] I have confirmed that this should be classified as an enhancement 
rather than a bug/feature.
   
   
   ### Summary
   
   目前在pop机制中使用的retry topic的格式是形如 
"%RETRY%group_topic",其中分隔符"_"是一个合法字符,可以被使用在topic或者group中,因此会导致两个问题。
   
   1. pop retry topic重复,比如由group_a,topic组成的retry topic,和由group,a_topic组成的retry 
topic均为%RETRY%group_a_topic
   2. 由于采用了合法字符"_"作为分隔符,因此没办法根据retry 
topic反向得出group和topic,在消息通知和需要拆分group的场景都会存在问题
   
   因此本方案提出了pop retry topic 
v2,以"/"为分割符,即形如"%RETRY%group/topic",其中"/"为topic和group无法使用的字符,因此解决了上述两个问题,同时/也隐式的表达了订阅的含义。
   
   
   Currently, in the pop mechanism, the format used for the retry topic is as 
the form of "%RETRY%group_topic". The underscore character "_" serves as a 
valid separator, which can be used within both the topic and group. 
Consequently, this situation leads to two issues:
   
   1. Repetition of pop retry topics: For instance, a retry topic composed of 
group_a and topic, and another retry topic composed of group and a_topic, both 
result in "%RETRY%group_a_topic".
   2. Due to the utilization of the underscore character "_" as a separator, it 
becomes impossible to deduce the group and topic from the retry topic. This 
presents challenges in scenarios involving message notifications and the need 
to split the group.
   
   Therefore, this proposal suggests the implementation of pop retry topic v2, 
employing the forward slash "/" as the separator. The new format would appear 
as "%RETRY%group/topic". Since "/" is not a permissible character in either 
topics or groups, it effectively resolves the aforementioned issues. 
Furthermore, the use of "/" implicitly expresses the subscription meaning.
   
   ### Motivation
   
   Fix the issue of original pop retry topic.
   
   ### Describe the Solution You'd Like
   
   Retry topic v2 as the format of "%RETRY%group/topic" where "/" is the 
separator.
   
   ### Describe Alternatives You've Considered
   
   No
   
   ### Additional Context
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@rocketmq.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to