Erik1288 opened a new issue #3634:
URL: https://github.com/apache/rocketmq/issues/3634


   The issue tracker is **ONLY** used for bug report(feature request need to 
follow [RIP 
process](https://github.com/apache/rocketmq/wiki/RocketMQ-Improvement-Proposal)).
 Keep in mind, please check whether there is an existing same report before 
your raise a new one.
   
   Alternately (especially if your communication is not a bug report), you can 
send mail to our [mailing lists](http://rocketmq.apache.org/about/contact/). We 
welcome any friendly suggestions, bug fixes, collaboration and other 
improvements.
   
   Please ensure that your bug report is clear and that it is complete. 
Otherwise, we may be unable to understand it or to reproduce it, either of 
which would prevent us from fixing the bug. We strongly recommend the 
report(bug report or feature request) could include some hints as the following:
   
   **FEATURE REQUEST**
   
   1. Please describe the feature you are requesting.
   * Introducing BatchConsumeQueue index to improve throughput for BatchMessage.
   * Refactor consume queue interface.
   
   2. Provide any additional detail on your proposed use case for this feature.
   * When Batch Consume Queue is introduced, each BatchMessage is no longer 
treated as a collection of sub-messages, but as an independent message.
           * When receiving a BatchMessage, the engine treats a BatchMessage as 
a normal message.
           * When indexing a BatchMessage,the engine will construct one index 
item for a single batch.
           * When consuming a BatchMessage,the engine will access index only 
once for a single batch.
           * End-to-end compression/uncompression will be supported on 
BatchMessage on the fly.
   
   3. Indicate the importance of this issue to you (blocker, must-have, 
should-have, nice-to-have). Are you currently using any workarounds to address 
this issue?
   It's 'nice-to-have'.
   No.
   
   4. If there are some sub-tasks using -[] for each subtask and create a 
corresponding issue to map to the sub task:
   
   * Implement client-side and server-side batch consume queue in broker.
   * Implement historic consume queue and batch consume queue converter.
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to