[
https://issues.apache.org/jira/browse/CASSANDRA-19965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17923760#comment-17923760
]
Maxwell Guo edited comment on CASSANDRA-19965 at 2/13/25 9:42 AM:
------------------------------------------------------------------
see the [DISCUSS|
https://lists.apache.org/[email protected]:lte=1M:WHAT%20IS%20THE%20STATUS]
for TRIGGERS , we are not going to support triggers this time ,so TRIGGERS and
ALL options are not going to be supported .
As the system_schema.indexes stores the definitions of secondary indexes, we
cannot use INDEXES as a keyword. Therefore, the grammar for CREATE TABLE LIKE
to clone indexes together has been changed
{code:java}
CREATE TABLE ttb LIKE stb WITH ALL INDEXES;
{code}
was (Author: maxwellguo):
see the [DISCUSS|
https://lists.apache.org/[email protected]:lte=1M:WHAT%20IS%20THE%20STATUS]
for TRIGGERS , we are not going to support triggers this time ,so TRIGGERS and
ALL options are not going to be supported .
> CREATE TABLE LIKE with INDEX/ TRIGGER /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: Maxwell Guo
> Assignee: Maxwell Guo
> 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]
