[jira] [Updated] (CASSANDRA-14706) Support "IF EXISTS/IF NOT EXISTS" for all clauses of "ALTER TABLE"

2019-02-15 Thread Dmitry Lazurkin (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitry Lazurkin updated CASSANDRA-14706:

Component/s: CQL/Syntax
 CQL/Interpreter

> Support "IF EXISTS/IF NOT EXISTS" for all clauses of "ALTER TABLE"
> --
>
> Key: CASSANDRA-14706
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14706
> Project: Cassandra
>  Issue Type: New Feature
>  Components: CQL/Interpreter, CQL/Syntax, Legacy/CQL
>Reporter: Dmitry Lazurkin
>Priority: Minor
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Like so:
> {noformat}
> ALTER TABLE  ALTER  TYPE ;
> ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ]  ;
> ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ] ( 
> , .  );
> ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ;
> ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ( 
> ,.);
> ALTER TABLE [ IF EXISTS ]  RENAME [ IF EXISTS ]  TO ;
> ALTER TABLE [ IF EXISTS ]  WITH  = ;
> {noformat}
> I think common IF EXISTS/IF NOT EXISTS clause for ADD/DROP/RENAME better than 
> clause for each column.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Comment Edited] (CASSANDRA-14706) Support "IF EXISTS/IF NOT EXISTS" for all clauses of "ALTER TABLE"

2018-10-03 Thread Dmitry Lazurkin (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-14706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637631#comment-16637631
 ] 

Dmitry Lazurkin edited comment on CASSANDRA-14706 at 10/3/18 11:48 PM:
---

RDBMS has DDL-transactions. So this is not so crucial for it. But C* migrations 
aren't so comfortable without this feature. If you have up-migration with many 
statements then you can't restart up-migration after error in middle and you 
can't start down-migration. You need manual revert of all statement before 
error.


was (Author: dmitry.lazurkin):
RDBMS have DDL-transactions. So this is not so crucial for it. But C* 
migrations aren't so comfortable without this feature. If you have up-migration 
with many statements then you can't restart up-migration after error in middle 
and you can't start down-migration. You need manual revert of all statement 
before error.

> Support "IF EXISTS/IF NOT EXISTS" for all clauses of "ALTER TABLE"
> --
>
> Key: CASSANDRA-14706
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14706
> Project: Cassandra
>  Issue Type: New Feature
>Reporter: Dmitry Lazurkin
>Priority: Minor
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Like so:
> {noformat}
> ALTER TABLE  ALTER  TYPE ;
> ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ]  ;
> ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ] ( 
> , .  );
> ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ;
> ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ( 
> ,.);
> ALTER TABLE [ IF EXISTS ]  RENAME [ IF EXISTS ]  TO ;
> ALTER TABLE [ IF EXISTS ]  WITH  = ;
> {noformat}
> I think common IF EXISTS/IF NOT EXISTS clause for ADD/DROP/RENAME better than 
> clause for each column.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-14706) Support "IF EXISTS/IF NOT EXISTS" for all clauses of "ALTER TABLE"

2018-10-03 Thread Dmitry Lazurkin (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-14706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637631#comment-16637631
 ] 

Dmitry Lazurkin commented on CASSANDRA-14706:
-

RDBMS have DDL-transactions. So this is not so crucial for it. But C* 
migrations aren't so comfortable without this feature. If you have up-migration 
with many statements then you can't restart up-migration after error in middle 
and you can't start down-migration. You need manual revert of all statement 
before error.

> Support "IF EXISTS/IF NOT EXISTS" for all clauses of "ALTER TABLE"
> --
>
> Key: CASSANDRA-14706
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14706
> Project: Cassandra
>  Issue Type: New Feature
>Reporter: Dmitry Lazurkin
>Priority: Minor
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Like so:
> {noformat}
> ALTER TABLE  ALTER  TYPE ;
> ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ]  ;
> ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ] ( 
> , .  );
> ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ;
> ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ( 
> ,.);
> ALTER TABLE [ IF EXISTS ]  RENAME [ IF EXISTS ]  TO ;
> ALTER TABLE [ IF EXISTS ]  WITH  = ;
> {noformat}
> I think common IF EXISTS/IF NOT EXISTS clause for ADD/DROP/RENAME better than 
> clause for each column.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-14706) Support "IF EXISTS/IF NOT EXISTS" for all clauses of "ALTER TABLE"

2018-09-08 Thread Dmitry Lazurkin (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitry Lazurkin updated CASSANDRA-14706:

Description: 
Like so:
{noformat}
ALTER TABLE  ALTER  TYPE ;
ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ]  ;
ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ] ( 
, .  );
ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ;
ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ( 
,.);
ALTER TABLE [ IF EXISTS ]  RENAME [ IF EXISTS ]  TO ;
ALTER TABLE [ IF EXISTS ]  WITH  = ;
{noformat}
I think common IF EXISTS/IF NOT EXISTS clause for ADD/DROP/RENAME better than 
clause for each column.

  was:
Like so:
{noformat}
ALTER TABLE  ALTER  TYPE ;
ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ]  ;
ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ] ( 
, .  );
ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ;
ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ( 
,.);
ALTER TABLE [ IF EXISTS ]  RENAME [ IF EXISTS ]  TO ;
ALTER TABLE [ IF EXISTS ]  WITH  = ;
{noformat}

I think common IF EXISTS/IF NOT EXISTS clause for ADD/DROP better than clause 
for each column.


> Support "IF EXISTS/IF NOT EXISTS" for all clauses of "ALTER TABLE"
> --
>
> Key: CASSANDRA-14706
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14706
> Project: Cassandra
>  Issue Type: New Feature
>Reporter: Dmitry Lazurkin
>Priority: Minor
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Like so:
> {noformat}
> ALTER TABLE  ALTER  TYPE ;
> ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ]  ;
> ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ] ( 
> , .  );
> ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ;
> ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ( 
> ,.);
> ALTER TABLE [ IF EXISTS ]  RENAME [ IF EXISTS ]  TO ;
> ALTER TABLE [ IF EXISTS ]  WITH  = ;
> {noformat}
> I think common IF EXISTS/IF NOT EXISTS clause for ADD/DROP/RENAME better than 
> clause for each column.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Issue Comment Deleted] (CASSANDRA-14706) Support "IF EXISTS/IF NOT EXISTS" for all clauses of "ALTER TABLE"

2018-09-08 Thread Dmitry Lazurkin (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitry Lazurkin updated CASSANDRA-14706:

Comment: was deleted

(was: Where can I change CQL documentation?)

> Support "IF EXISTS/IF NOT EXISTS" for all clauses of "ALTER TABLE"
> --
>
> Key: CASSANDRA-14706
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14706
> Project: Cassandra
>  Issue Type: New Feature
>Reporter: Dmitry Lazurkin
>Priority: Minor
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Like so:
> {noformat}
> ALTER TABLE  ALTER  TYPE ;
> ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ]  ;
> ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ] ( 
> , .  );
> ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ;
> ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ( 
> ,.);
> ALTER TABLE [ IF EXISTS ]  RENAME [ IF EXISTS ]  TO ;
> ALTER TABLE [ IF EXISTS ]  WITH  = ;
> {noformat}
> I think common IF EXISTS/IF NOT EXISTS clause for ADD/DROP better than clause 
> for each column.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Comment Edited] (CASSANDRA-14706) Support "IF EXISTS/IF NOT EXISTS" for all clauses of "ALTER TABLE"

2018-09-08 Thread Dmitry Lazurkin (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-14706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608034#comment-16608034
 ] 

Dmitry Lazurkin edited comment on CASSANDRA-14706 at 9/8/18 12:27 PM:
--

Where can I change CQL documentation?


was (Author: dmitry.lazurkin):
Where I can change CQL documentation?

> Support "IF EXISTS/IF NOT EXISTS" for all clauses of "ALTER TABLE"
> --
>
> Key: CASSANDRA-14706
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14706
> Project: Cassandra
>  Issue Type: New Feature
>Reporter: Dmitry Lazurkin
>Priority: Minor
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Like so:
> {noformat}
> ALTER TABLE  ALTER  TYPE ;
> ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ]  ;
> ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ] ( 
> , .  );
> ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ;
> ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ( 
> ,.);
> ALTER TABLE [ IF EXISTS ]  RENAME [ IF EXISTS ]  TO ;
> ALTER TABLE [ IF EXISTS ]  WITH  = ;
> {noformat}
> I think common IF EXISTS/IF NOT EXISTS clause for ADD/DROP better than clause 
> for each column.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-14706) Support "IF EXISTS/IF NOT EXISTS" for all clauses of "ALTER TABLE"

2018-09-08 Thread Dmitry Lazurkin (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-14706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608034#comment-16608034
 ] 

Dmitry Lazurkin commented on CASSANDRA-14706:
-

Where I can change CQL documentation?

> Support "IF EXISTS/IF NOT EXISTS" for all clauses of "ALTER TABLE"
> --
>
> Key: CASSANDRA-14706
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14706
> Project: Cassandra
>  Issue Type: New Feature
>Reporter: Dmitry Lazurkin
>Priority: Minor
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Like so:
> {noformat}
> ALTER TABLE  ALTER  TYPE ;
> ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ]  ;
> ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ] ( 
> , .  );
> ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ;
> ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ( 
> ,.);
> ALTER TABLE [ IF EXISTS ]  RENAME [ IF EXISTS ]  TO ;
> ALTER TABLE [ IF EXISTS ]  WITH  = ;
> {noformat}
> I think common IF EXISTS/IF NOT EXISTS clause for ADD/DROP better than clause 
> for each column.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Created] (CASSANDRA-14706) Support "IF EXISTS/IF NOT EXISTS" for all clauses of "ALTER TABLE"

2018-09-08 Thread Dmitry Lazurkin (JIRA)
Dmitry Lazurkin created CASSANDRA-14706:
---

 Summary: Support "IF EXISTS/IF NOT EXISTS" for all clauses of 
"ALTER TABLE"
 Key: CASSANDRA-14706
 URL: https://issues.apache.org/jira/browse/CASSANDRA-14706
 Project: Cassandra
  Issue Type: New Feature
Reporter: Dmitry Lazurkin


Like so:
{noformat}
ALTER TABLE  ALTER  TYPE ;
ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ]  ;
ALTER TABLE [ IF EXISTS ]  ADD [ IF NOT EXISTS ] ( 
, .  );
ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ;
ALTER TABLE [ IF EXISTS ]  DROP [ IF EXISTS ] ( 
,.);
ALTER TABLE [ IF EXISTS ]  RENAME [ IF EXISTS ]  TO ;
ALTER TABLE [ IF EXISTS ]  WITH  = ;
{noformat}

I think common IF EXISTS/IF NOT EXISTS clause for ADD/DROP better than clause 
for each column.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org