You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kvrocks.apache.org by "PragmaTwice (via GitHub)" <gi...@apache.org> on 2024/10/08 15:41:42 UTC
[I] Add the supporting status of subcommands in the website [kvrocks]
PragmaTwice opened a new issue, #2587:
URL: https://github.com/apache/kvrocks/issues/2587
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/kvrocks/issues) and found no similar issues.
### Motivation
https://kvrocks.apache.org/docs/supported-commands
In this page users can check if a command is supported or not.
For CLUSTER and CLUSTERX we have a list to state the supporting status of every subcommands of these command,
but for many other commands we don't, e.g. CLIENT, SCRIPT...
We need to add subcommand supporting list for every command that have subcommands.
### Solution
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
--
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: issues-unsubscribe@kvrocks.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Add the supporting status of subcommands in the website [kvrocks]
Posted by "beingPro007 (via GitHub)" <gi...@apache.org>.
beingPro007 commented on issue #2587:
URL: https://github.com/apache/kvrocks/issues/2587#issuecomment-2406545220
@PragmaTwice
**Could you clarify which specific commands currently lack subcommand listings?**
I've noticed that commands like CLUSTER and CLUSTERX have detailed subcommand lists, but other commands such as CLIENT and SCRIPT don't. To improve the consistency of the documentation, it would be helpful to know which commands require subcommand listings to be added. Could you provide a list of such commands so we can address this gap?
--
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: issues-unsubscribe@kvrocks.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Add the supporting status of subcommands in the website [kvrocks]
Posted by "beingPro007 (via GitHub)" <gi...@apache.org>.
beingPro007 commented on issue #2587:
URL: https://github.com/apache/kvrocks/issues/2587#issuecomment-2406523070
@PragmaTwice i would be happy if you assign this to me!!!
--
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: issues-unsubscribe@kvrocks.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Add the supporting status of subcommands in the website [kvrocks]
Posted by "PragmaTwice (via GitHub)" <gi...@apache.org>.
PragmaTwice closed issue #2587: Add the supporting status of subcommands in the website
URL: https://github.com/apache/kvrocks/issues/2587
--
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: issues-unsubscribe@kvrocks.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Add the supporting status of subcommands in the website [kvrocks]
Posted by "beingPro007 (via GitHub)" <gi...@apache.org>.
beingPro007 commented on issue #2587:
URL: https://github.com/apache/kvrocks/issues/2587#issuecomment-2406576954
> > @PragmaTwice **Could you clarify which specific commands currently lack subcommand listings?**
> >
> > I've noticed that commands like CLUSTER and CLUSTERX have detailed subcommand lists, but other commands such as CLIENT and SCRIPT don't. To improve the consistency of the documentation, it would be helpful to know which commands require subcommand listings to be added. Could you provide a list of such commands so we can address this gap?
>
> Hi, thank you for your interest and question.
>
> You can check Redis documentation to know if a command has subcommands. All commands that have subcommands need to be listed.
>
> BTW I recommend to be familiar with Redis before taking this task. Then you can easily identify what kind of commands are likely to have subcommands.
>
Ok let me first be familiar with redis. Thank you for your consideration
--
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: issues-unsubscribe@kvrocks.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Add the supporting status of subcommands in the website [kvrocks]
Posted by "PragmaTwice (via GitHub)" <gi...@apache.org>.
PragmaTwice commented on issue #2587:
URL: https://github.com/apache/kvrocks/issues/2587#issuecomment-2406564519
> @PragmaTwice **Could you clarify which specific commands currently lack subcommand listings?**
>
> I've noticed that commands like CLUSTER and CLUSTERX have detailed subcommand lists, but other commands such as CLIENT and SCRIPT don't. To improve the consistency of the documentation, it would be helpful to know which commands require subcommand listings to be added. Could you provide a list of such commands so we can address this gap?
Hi, thank you for your interest and question.
You can check Redis documentation to know if a command has subcommands. All commands that have subcommands need to be listed.
BTW I recommend to be familiar with Redis before taking this task. Then you can easily identify what kind of commands are likely to have subcommands.
--
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: issues-unsubscribe@kvrocks.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org