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

Biju Nair edited comment on PHOENIX-2809 at 4/4/16 10:42 AM:
-------------------------------------------------------------

[~sergey.soldatov] agreed that the statement shouldn't fail, but at the 
sametime it should not create a duplicate column. no? In the example provided 
duplicate column {{T1}} got created.


was (Author: gsbiju):
[~sergey.soldatov] agreed that the statement shouldn't fail, but at the 
sometime it should not create a duplicate column. no? In the example provided 
duplicate column {{T1}} got created.

> Alter table doesn't take into account current table definition
> --------------------------------------------------------------
>
>                 Key: PHOENIX-2809
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2809
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Biju Nair
>
> {{Alter table}} to add a new column with the column definition as an existing 
> column in the table succeeds while the expectation will be that the alter 
> will fail. Following is an example.
> {noformat}
> 0: jdbc:phoenix:localhost:2181:/hbase> create table test_alter (TI tinyint 
> not null primary key);
> No rows affected (1.299 seconds)
> 0: jdbc:phoenix:localhost:2181:/hbase> alter table test_alter add if not 
> exists TI tinyint, col1 varchar;
> No rows affected (15.962 seconds)
> 0: jdbc:phoenix:localhost:2181:/hbase> upsert into test_alter values 
> (1,2,'add');
> 1 row affected (0.008 seconds)
> 0: jdbc:phoenix:localhost:2181:/hbase> select * from test_alter;
> +-----+-----+-------+
> | TI  | TI  | COL1  |
> +-----+-----+-------+
> | 1   | 1   | add   |
> +-----+-----+-------+
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to