lizhiboo commented on issue #2156:
URL: https://github.com/apache/rocketmq/issues/2156#issuecomment-785065206


   > **FEATURE REQUEST**
   > 
   > 1. Please describe the feature you are requesting.
   > 
   > add beginTime and EndTime to queryMsgByKey command
   > 
   > 1. Provide any additional detail on your proposed use case for this 
feature.
   > 
   > now, queryMsgByKey looks like below:
   > 
   > ```
   > -> %  mqadmin queryMsgByKey
   > usage: mqadmin queryMsgByKey [-h] -k <arg> [-n <arg>] -t <arg>
   >  -h,--help                Print help
   >  -k,--msgKey <arg>        Message Key
   >  -n,--namesrvAddr <arg>   Name server address list, eg: 
192.168.0.1:9876;192.168.0.2:9876
   >  -t,--topic <arg>         topic name
   > ```
   > 
   > after proposed, we support like below:
   > 
   > ```
   > -> %  mqadmin queryMsgByKey
   > usage: mqadmin queryMsgByKey [-h] -k <arg> [-n <arg>] -t <arg>
   >  -h,--help                Print help
   >  -k,--msgKey <arg>        Message Key
   >  -n,--namesrvAddr <arg>   Name server address list, eg: 
192.168.0.1:9876;192.168.0.2:9876
   >  -t,--topic <arg>         topic name
   >  -s, --startms       default 0, 
   >  -e, --endms        default Long.MAX_VALUE
   > ```
   > 
   > 1. 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?
   > 2. If there are some sub-tasks using -[] for each subtask and create a 
corresponding issue to map to the sub task:
   > 
   > * [sub-task1-issue-number](example_sub_issue1_link_here): sub-task1 
description here,
   > * [sub-task2-issue-number](example_sub_issue2_link_here): sub-task2 
description here,
   > * ...
   
   Can u submit a pr to fulfill it ?


----------------------------------------------------------------
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.

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


Reply via email to