[
https://issues.apache.org/jira/browse/CASSANDRA-19965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17929842#comment-17929842
]
Stefan Miklosovic commented on CASSANDRA-19965:
-----------------------------------------------
We should give it a little bit more love (1)
I do not understand why we would not reuse the methods you have introduced in
CopyTableStatement.
(1)
https://github.com/instaclustr/cassandra/commit/f1cc50fd671eaf78772196cb419a948d265a14db
> CREATE TABLE LIKE with INDEX / ALL option
> -------------------------------------------
>
> Key: CASSANDRA-19965
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19965
> Project: Apache Cassandra
> Issue Type: New Feature
> Components: Cluster/Schema, CQL/Syntax
> Reporter: guo Maxwell
> Assignee: guo Maxwell
> Priority: Normal
> Fix For: 5.x
>
>
> no matter Copy table with indexes or triggers under same keyspace or
> differenet.
> The indexes and trigger name should be different from the source in case of
> conflict.
> we need to
> 1.Adding cql parser for ALL/INDEX/TRIGGER when doing create table like
> 2.Automatic completion of keywords(LIKE/ALL/INDEX/TRIGGER) and function hints
> (the source table and target table explain_completion when doing table copy)
> at the cqlsh level.
> in pylib/cqlshlib/cql3handling.py and the test in
> pylib/cqlshlib/test/test_cqlsh_completion.py.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
