[tools] QueryMsgByKeySubCommand should support timeRange

[xujianhai666]

FEATURE REQUEST

1. Please describe the feature you are requesting.

add beginTime and EndTime to queryMsgByKey command

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

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

3. 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: sub-task1 description here,
• sub-task2-issue-number: sub-task2 description here,
• ...

[jjz921024]

Is this issue finish?

[lizhiboo]

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: sub-task1 description here,
• sub-task2-issue-number: sub-task2 description here,
• ...

Can u submit a pr to fulfill it ?

[github-actions]

This issue is stale because it has been open for 365 days with no activity. It will be closed in 3 days if no further activity occurs.

[github-actions]

This issue was closed because it has been inactive for 3 days since being marked as stale.