Hi Zhendong, Nice to see your feedback.
In terms of Batched Messages. I believe we can solve it this way In message headers IDL, we have an enum, flagging if the data layout is single or batch/composite or other format. If the enum says single, then the body is user data. If enum says composite, then body of the frame should be considered as several nested messages. The format of the nested messages may be some compact representation. We may add one more task, tackling this issue. Zhanhui Li On Mon, Oct 10, 2022 at 11:13 AM dongeforever <dongefore...@apache.org> wrote: > Nice try. > Looking forward to the detailed layout. > > By the way, the new data format may need to consider more about the batch > record, several messages in one record end to end (from producers to > consumers). > > > Zhanhui Li <lizhan...@gmail.com> 于2022年10月9日周日 21:52写道： > > > Hi, > > > > RocketMQ has stuck to its data format for many years and we are > > experiencing many blocking problems originating from this design. > > > > RIP-47 https://github.com/apache/rocketmq/wiki/RIP-47-Data-Layout-V2 is > to > > designed to solve the mentioned issues. > > > > Please review the design. Constructive feedback and comments are > > anticipated. > > > > It is a major RIP to RocketMQ, multiple critical data paths are involved. > > It's welcome to join this RIP if you are interested. > > > > Zhanhui Li > > >
