You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Yundi Chen (Jira)" <ji...@apache.org> on 2022/09/19 03:11:00 UTC
[jira] [Commented] (CASSANDRA-15046) Add a "history" command to cqlsh. Perhaps "show history"?
[ https://issues.apache.org/jira/browse/CASSANDRA-15046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17606401#comment-17606401 ]
Yundi Chen commented on CASSANDRA-15046:
----------------------------------------
The current patch implements the feature in its minimally viable form. Here's some of my ideas for improvement to current patch:
# allow an input argument to control how many commands will be listed.
# showing the timestamp of when each command is executed.
# showing whether each command is valid/successfully executed, OR, showing only the successfully executed commands.
Thoughts?
> Add a "history" command to cqlsh. Perhaps "show history"?
> ----------------------------------------------------------
>
> Key: CASSANDRA-15046
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15046
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Interpreter
> Reporter: Wes Peters
> Assignee: Yundi Chen
> Priority: Low
> Labels: ghc-lhf, lhf
> Fix For: 4.x
>
>
> I was trying to capture some create key space and create table commands from a running cqlsh, and found there was no equivalent to the '\s' history command in Postgres' psql shell. It's a great tool for figuring out what you were doing yesterday.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org