[
https://issues.apache.org/jira/browse/CASSANDRA-15046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17608463#comment-17608463
]
Ekaterina Dimitrova edited comment on CASSANDRA-15046 at 9/23/22 1:48 AM:
--------------------------------------------------------------------------
Hi[~ychen02],
I noticed you linked only the last commit. Though I found your trunk branch:)
May I ask you to rebase your patch commits on top of trunk? Also, we normally
create a new branch. You can name it anyway but very often we see people name
them with ticket number-version we work on. Opening a PR will also make it easy
to review. Thanks in advance
was (Author: e.dimitrova):
Hi[~ychen02],
I noticed you linked only the last commit. Though I found your trunk branch:)
May I ask you to rebase your patch commits on top of trunk. Also, we normally
create a new branch. You can name it anyway but very often we see people name
them with ticket number-version we work on. Opening a PR will also make it easy
to review. Thanks in advance
> 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]
