[
https://issues.apache.org/jira/browse/CASSANDRA-15046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yundi Chen updated CASSANDRA-15046:
-----------------------------------
Test and Documentation Plan:
Original Patch PR: [https://github.com/apache/cassandra/pull/1866/files]
[NEW - NEEDS REVIEW] 09/22/22: documentation patch
[https://github.com/apache/cassandra/commit/31f9a566bb70368dbffddeb672196355efe7ebb0]
Unit tests to be implemented:
1. check "history" command outputs correct length of results
2. check "history" command outputs correct contents & order
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?
was:
Patch PR: [https://github.com/apache/cassandra/pull/1866/files]
Documentation: Will add documentation in
doc/modules/cassandra/pages/tools/cqlsh.adoc and CHANGES.md describing the
HISTORY command, following the documentation style of the other cqlsh commands.
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?
Status: Patch Available (was: In Progress)
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
