[jira] [Comment Edited] (SPARK-21823) ALTER TABLE table statements such as RENAME and CHANGE columns should raise error if there are any dependent constraints.
[
https://issues.apache.org/jira/browse/SPARK-21823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17025611#comment-17025611
]
sakshi chourasia edited comment on SPARK-21823 at 1/30/20 5:20 AM:
---
Hi [~ksunitha]
I work with spark sql. Need this command to alter the column name. I have some
100+ table with 4 columns to be renamed in each, present in Prod and Dev env.
May I know when we are planning to let this command out.
was (Author: sakshi49):
Hi [~ksunitha]
I work with spark sql. Need this command to alter the column name. I have some
100+ table with 4 columns to be renamed in each present in Prod and Dev env.
May I know when we are planning to let this command out.
> ALTER TABLE table statements such as RENAME and CHANGE columns should raise
> error if there are any dependent constraints.
> -
>
> Key: SPARK-21823
> URL: https://issues.apache.org/jira/browse/SPARK-21823
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
>Affects Versions: 3.0.0
>Reporter: Suresh Thalamati
>Priority: Major
>
> Following ALTER TABLE DDL statements will impact the informational
> constraints defined on a table:
> {code:sql}
> ALTER TABLE name RENAME TO new_name
> ALTER TABLE name CHANGE column_name new_name new_type
> {code}
> Spark SQL should raise errors if there are
informational constraints
> defined on the columns affected by the ALTER and let the user drop
> constraints before proceeding with the DDL. In the future we can enhance the
> ALTER to automatically fix up the constraint definition in the catalog when
> possible, and not raise error
> When spark adds support for DROP/REPLACE of columns they will impact
> informational constraints.
> {code:sql}
> ALTER TABLE name DROP [COLUMN] column_name
> ALTER TABLE name REPLACE COLUMNS (col_spec[, col_spec ...])
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Comment Edited] (SPARK-21823) ALTER TABLE table statements such as RENAME and CHANGE columns should raise error if there are any dependent constraints.
[
https://issues.apache.org/jira/browse/SPARK-21823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17025611#comment-17025611
]
sakshi chourasia edited comment on SPARK-21823 at 1/30/20 3:56 AM:
---
Hi [~ksunitha]
I work with spark sql. Need this command to alter the column name. I have some
100+ table with 4 columns to be renamed in each present in Prod and Dev env.
May I know when we are planning to let this command out.
was (Author: sakshi49):
Hi [~ksunitha]
I work with spark sql. Need this command to alter the table name. I have some
100+ table present in Prod and Dev env. May I know when we are planning to let
this command out.
> ALTER TABLE table statements such as RENAME and CHANGE columns should raise
> error if there are any dependent constraints.
> -
>
> Key: SPARK-21823
> URL: https://issues.apache.org/jira/browse/SPARK-21823
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
>Affects Versions: 3.0.0
>Reporter: Suresh Thalamati
>Priority: Major
>
> Following ALTER TABLE DDL statements will impact the informational
> constraints defined on a table:
> {code:sql}
> ALTER TABLE name RENAME TO new_name
> ALTER TABLE name CHANGE column_name new_name new_type
> {code}
> Spark SQL should raise errors if there are
informational constraints
> defined on the columns affected by the ALTER and let the user drop
> constraints before proceeding with the DDL. In the future we can enhance the
> ALTER to automatically fix up the constraint definition in the catalog when
> possible, and not raise error
> When spark adds support for DROP/REPLACE of columns they will impact
> informational constraints.
> {code:sql}
> ALTER TABLE name DROP [COLUMN] column_name
> ALTER TABLE name REPLACE COLUMNS (col_spec[, col_spec ...])
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Comment Edited] (SPARK-21823) ALTER TABLE table statements such as RENAME and CHANGE columns should raise error if there are any dependent constraints.
[
https://issues.apache.org/jira/browse/SPARK-21823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17025611#comment-17025611
]
sakshi chourasia edited comment on SPARK-21823 at 1/29/20 6:52 AM:
---
Hi [~ksunitha]
I work with spark sql. Need this command to alter the table name. I have some
100+ table present in Prod and Dev env. May I know when we are planning to let
this command out.
was (Author: sakshi49):
I work with spark sql. Need this command to alter the table name. I have some
100+ table present in Prod and Dev env. May I know when we are planning to let
this command out.
> ALTER TABLE table statements such as RENAME and CHANGE columns should raise
> error if there are any dependent constraints.
> -
>
> Key: SPARK-21823
> URL: https://issues.apache.org/jira/browse/SPARK-21823
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
>Affects Versions: 3.0.0
>Reporter: Suresh Thalamati
>Priority: Major
>
> Following ALTER TABLE DDL statements will impact the informational
> constraints defined on a table:
> {code:sql}
> ALTER TABLE name RENAME TO new_name
> ALTER TABLE name CHANGE column_name new_name new_type
> {code}
> Spark SQL should raise errors if there are
informational constraints
> defined on the columns affected by the ALTER and let the user drop
> constraints before proceeding with the DDL. In the future we can enhance the
> ALTER to automatically fix up the constraint definition in the catalog when
> possible, and not raise error
> When spark adds support for DROP/REPLACE of columns they will impact
> informational constraints.
> {code:sql}
> ALTER TABLE name DROP [COLUMN] column_name
> ALTER TABLE name REPLACE COLUMNS (col_spec[, col_spec ...])
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Comment Edited] (SPARK-21823) ALTER TABLE table statements such as RENAME and CHANGE columns should raise error if there are any dependent constraints.
[
https://issues.apache.org/jira/browse/SPARK-21823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16474474#comment-16474474
]
Sunitha Kambhampati edited comment on SPARK-21823 at 5/14/18 5:01 PM:
--
I have the changes for this. Once the dependent SPARK-21784 is reviewed and
merged, I can submit changes for this issue.
was (Author: ksunitha):
I have the changes for this. Once the dependent SPARK-21784 is reviewed and
delivered, I can submit changes for this issue.
> ALTER TABLE table statements such as RENAME and CHANGE columns should raise
> error if there are any dependent constraints.
> -
>
> Key: SPARK-21823
> URL: https://issues.apache.org/jira/browse/SPARK-21823
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
>Affects Versions: 3.0.0
>Reporter: Suresh Thalamati
>Priority: Major
>
> Following ALTER TABLE DDL statements will impact the informational
> constraints defined on a table:
> {code:sql}
> ALTER TABLE name RENAME TO new_name
> ALTER TABLE name CHANGE column_name new_name new_type
> {code}
> Spark SQL should raise errors if there are
informational constraints
> defined on the columns affected by the ALTER and let the user drop
> constraints before proceeding with the DDL. In the future we can enhance the
> ALTER to automatically fix up the constraint definition in the catalog when
> possible, and not raise error
> When spark adds support for DROP/REPLACE of columns they will impact
> informational constraints.
> {code:sql}
> ALTER TABLE name DROP [COLUMN] column_name
> ALTER TABLE name REPLACE COLUMNS (col_spec[, col_spec ...])
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
