[jira] [Updated] (PHOENIX-1614) ALTER TABLE ADD IF NOT EXISTS doesn't work as expected
[ https://issues.apache.org/jira/browse/PHOENIX-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-1614: - Fix Version/s: 5.1.0 > ALTER TABLE ADD IF NOT EXISTS doesn't work as expected > -- > > Key: PHOENIX-1614 > URL: https://issues.apache.org/jira/browse/PHOENIX-1614 > Project: Phoenix > Issue Type: Bug >Reporter: Gabriel Reid >Assignee: Toshihiro Suzuki >Priority: Major > Labels: argus > Fix For: 4.15.0, 5.1.0 > > Attachments: PHOENIX-1614-v2.patch, PHOENIX-1614-v3.patch, > PHOENIX-1614-v4.patch, PHOENIX-1614-v5.patch, PHOENIX-1614.patch > > > On an existing table table, executing "ALTER TABLE ADD IF NOT EXISTS > thisColAlreadyExists varchar, thisColDoesNotExist varchar", then > nothing will be changed in the table because thisColAlreadyExists > already exists. > Omitting the already-existing column from the statement, all new columns > do get created. > The general expectation would be that when you use ADD IF NOT EXISTS, all > non-existent columns will be added, and all existing columns in the > statement will just be ignored. There is already an integration test > (AlterTableIT#testAddVarCols) that actually demonstrates the current > behavior, although this is probably not correct. > As pointed out in the related mailing list thread [1], ALTER TABLE DROP > COLUMN likely suffers from the same issue. > 1. http://s.apache.org/LMT -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-1614) ALTER TABLE ADD IF NOT EXISTS doesn't work as expected
[ https://issues.apache.org/jira/browse/PHOENIX-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki updated PHOENIX-1614: -- Attachment: PHOENIX-1614-v5.patch > ALTER TABLE ADD IF NOT EXISTS doesn't work as expected > -- > > Key: PHOENIX-1614 > URL: https://issues.apache.org/jira/browse/PHOENIX-1614 > Project: Phoenix > Issue Type: Bug >Reporter: Gabriel Reid >Assignee: Toshihiro Suzuki >Priority: Major > Labels: argus > Fix For: 4.15.0 > > Attachments: PHOENIX-1614-v2.patch, PHOENIX-1614-v3.patch, > PHOENIX-1614-v4.patch, PHOENIX-1614-v5.patch, PHOENIX-1614.patch > > > On an existing table table, executing "ALTER TABLE ADD IF NOT EXISTS > thisColAlreadyExists varchar, thisColDoesNotExist varchar", then > nothing will be changed in the table because thisColAlreadyExists > already exists. > Omitting the already-existing column from the statement, all new columns > do get created. > The general expectation would be that when you use ADD IF NOT EXISTS, all > non-existent columns will be added, and all existing columns in the > statement will just be ignored. There is already an integration test > (AlterTableIT#testAddVarCols) that actually demonstrates the current > behavior, although this is probably not correct. > As pointed out in the related mailing list thread [1], ALTER TABLE DROP > COLUMN likely suffers from the same issue. > 1. http://s.apache.org/LMT -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-1614) ALTER TABLE ADD IF NOT EXISTS doesn't work as expected
[ https://issues.apache.org/jira/browse/PHOENIX-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki updated PHOENIX-1614: -- Attachment: PHOENIX-1614-v4.patch > ALTER TABLE ADD IF NOT EXISTS doesn't work as expected > -- > > Key: PHOENIX-1614 > URL: https://issues.apache.org/jira/browse/PHOENIX-1614 > Project: Phoenix > Issue Type: Bug >Reporter: Gabriel Reid >Assignee: Toshihiro Suzuki >Priority: Major > Labels: argus > Fix For: 4.15.0 > > Attachments: PHOENIX-1614-v2.patch, PHOENIX-1614-v3.patch, > PHOENIX-1614-v4.patch, PHOENIX-1614.patch > > > On an existing table table, executing "ALTER TABLE ADD IF NOT EXISTS > thisColAlreadyExists varchar, thisColDoesNotExist varchar", then > nothing will be changed in the table because thisColAlreadyExists > already exists. > Omitting the already-existing column from the statement, all new columns > do get created. > The general expectation would be that when you use ADD IF NOT EXISTS, all > non-existent columns will be added, and all existing columns in the > statement will just be ignored. There is already an integration test > (AlterTableIT#testAddVarCols) that actually demonstrates the current > behavior, although this is probably not correct. > As pointed out in the related mailing list thread [1], ALTER TABLE DROP > COLUMN likely suffers from the same issue. > 1. http://s.apache.org/LMT -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-1614) ALTER TABLE ADD IF NOT EXISTS doesn't work as expected
[ https://issues.apache.org/jira/browse/PHOENIX-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki updated PHOENIX-1614: -- Attachment: PHOENIX-1614-v3.patch > ALTER TABLE ADD IF NOT EXISTS doesn't work as expected > -- > > Key: PHOENIX-1614 > URL: https://issues.apache.org/jira/browse/PHOENIX-1614 > Project: Phoenix > Issue Type: Bug >Reporter: Gabriel Reid >Assignee: Toshihiro Suzuki >Priority: Major > Labels: argus > Fix For: 4.15.0 > > Attachments: PHOENIX-1614-v2.patch, PHOENIX-1614-v3.patch, > PHOENIX-1614.patch > > > On an existing table table, executing "ALTER TABLE ADD IF NOT EXISTS > thisColAlreadyExists varchar, thisColDoesNotExist varchar", then > nothing will be changed in the table because thisColAlreadyExists > already exists. > Omitting the already-existing column from the statement, all new columns > do get created. > The general expectation would be that when you use ADD IF NOT EXISTS, all > non-existent columns will be added, and all existing columns in the > statement will just be ignored. There is already an integration test > (AlterTableIT#testAddVarCols) that actually demonstrates the current > behavior, although this is probably not correct. > As pointed out in the related mailing list thread [1], ALTER TABLE DROP > COLUMN likely suffers from the same issue. > 1. http://s.apache.org/LMT -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-1614) ALTER TABLE ADD IF NOT EXISTS doesn't work as expected
[ https://issues.apache.org/jira/browse/PHOENIX-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki updated PHOENIX-1614: -- Attachment: PHOENIX-1614-v2.patch > ALTER TABLE ADD IF NOT EXISTS doesn't work as expected > -- > > Key: PHOENIX-1614 > URL: https://issues.apache.org/jira/browse/PHOENIX-1614 > Project: Phoenix > Issue Type: Bug >Reporter: Gabriel Reid >Assignee: Toshihiro Suzuki >Priority: Major > Labels: argus > Fix For: 4.15.0 > > Attachments: PHOENIX-1614-v2.patch, PHOENIX-1614.patch > > > On an existing table table, executing "ALTER TABLE ADD IF NOT EXISTS > thisColAlreadyExists varchar, thisColDoesNotExist varchar", then > nothing will be changed in the table because thisColAlreadyExists > already exists. > Omitting the already-existing column from the statement, all new columns > do get created. > The general expectation would be that when you use ADD IF NOT EXISTS, all > non-existent columns will be added, and all existing columns in the > statement will just be ignored. There is already an integration test > (AlterTableIT#testAddVarCols) that actually demonstrates the current > behavior, although this is probably not correct. > As pointed out in the related mailing list thread [1], ALTER TABLE DROP > COLUMN likely suffers from the same issue. > 1. http://s.apache.org/LMT -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-1614) ALTER TABLE ADD IF NOT EXISTS doesn't work as expected
[ https://issues.apache.org/jira/browse/PHOENIX-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki updated PHOENIX-1614: -- Attachment: PHOENIX-1614.patch > ALTER TABLE ADD IF NOT EXISTS doesn't work as expected > -- > > Key: PHOENIX-1614 > URL: https://issues.apache.org/jira/browse/PHOENIX-1614 > Project: Phoenix > Issue Type: Bug >Reporter: Gabriel Reid >Assignee: Toshihiro Suzuki >Priority: Major > Labels: argus > Fix For: 4.15.0 > > Attachments: PHOENIX-1614.patch > > > On an existing table table, executing "ALTER TABLE ADD IF NOT EXISTS > thisColAlreadyExists varchar, thisColDoesNotExist varchar", then > nothing will be changed in the table because thisColAlreadyExists > already exists. > Omitting the already-existing column from the statement, all new columns > do get created. > The general expectation would be that when you use ADD IF NOT EXISTS, all > non-existent columns will be added, and all existing columns in the > statement will just be ignored. There is already an integration test > (AlterTableIT#testAddVarCols) that actually demonstrates the current > behavior, although this is probably not correct. > As pointed out in the related mailing list thread [1], ALTER TABLE DROP > COLUMN likely suffers from the same issue. > 1. http://s.apache.org/LMT -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (PHOENIX-1614) ALTER TABLE ADD IF NOT EXISTS doesn't work as expected
[ https://issues.apache.org/jira/browse/PHOENIX-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-1614: -- Labels: argus (was: ) > ALTER TABLE ADD IF NOT EXISTS doesn't work as expected > -- > > Key: PHOENIX-1614 > URL: https://issues.apache.org/jira/browse/PHOENIX-1614 > Project: Phoenix > Issue Type: Bug >Reporter: Gabriel Reid >Assignee: Thomas D'Silva > Labels: argus > Fix For: 4.8.0 > > > On an existing table table, executing "ALTER TABLE ADD IF NOT EXISTS > thisColAlreadyExists varchar, thisColDoesNotExist varchar", then > nothing will be changed in the table because thisColAlreadyExists > already exists. > Omitting the already-existing column from the statement, all new columns > do get created. > The general expectation would be that when you use ADD IF NOT EXISTS, all > non-existent columns will be added, and all existing columns in the > statement will just be ignored. There is already an integration test > (AlterTableIT#testAddVarCols) that actually demonstrates the current > behavior, although this is probably not correct. > As pointed out in the related mailing list thread [1], ALTER TABLE DROP > COLUMN likely suffers from the same issue. > 1. http://s.apache.org/LMT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PHOENIX-1614) ALTER TABLE ADD IF NOT EXISTS doesn't work as expected
[ https://issues.apache.org/jira/browse/PHOENIX-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-1614: -- Fix Version/s: 4.8.0 > ALTER TABLE ADD IF NOT EXISTS doesn't work as expected > -- > > Key: PHOENIX-1614 > URL: https://issues.apache.org/jira/browse/PHOENIX-1614 > Project: Phoenix > Issue Type: Bug >Reporter: Gabriel Reid >Assignee: Thomas D'Silva > Labels: argus > Fix For: 4.8.0 > > > On an existing table table, executing "ALTER TABLE ADD IF NOT EXISTS > thisColAlreadyExists varchar, thisColDoesNotExist varchar", then > nothing will be changed in the table because thisColAlreadyExists > already exists. > Omitting the already-existing column from the statement, all new columns > do get created. > The general expectation would be that when you use ADD IF NOT EXISTS, all > non-existent columns will be added, and all existing columns in the > statement will just be ignored. There is already an integration test > (AlterTableIT#testAddVarCols) that actually demonstrates the current > behavior, although this is probably not correct. > As pointed out in the related mailing list thread [1], ALTER TABLE DROP > COLUMN likely suffers from the same issue. > 1. http://s.apache.org/LMT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PHOENIX-1614) ALTER TABLE ADD IF NOT EXISTS doesn't work as expected
[ https://issues.apache.org/jira/browse/PHOENIX-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-1614: -- Assignee: Thomas D'Silva > ALTER TABLE ADD IF NOT EXISTS doesn't work as expected > -- > > Key: PHOENIX-1614 > URL: https://issues.apache.org/jira/browse/PHOENIX-1614 > Project: Phoenix > Issue Type: Bug >Reporter: Gabriel Reid >Assignee: Thomas D'Silva > Labels: argus > Fix For: 4.8.0 > > > On an existing table table, executing "ALTER TABLE ADD IF NOT EXISTS > thisColAlreadyExists varchar, thisColDoesNotExist varchar", then > nothing will be changed in the table because thisColAlreadyExists > already exists. > Omitting the already-existing column from the statement, all new columns > do get created. > The general expectation would be that when you use ADD IF NOT EXISTS, all > non-existent columns will be added, and all existing columns in the > statement will just be ignored. There is already an integration test > (AlterTableIT#testAddVarCols) that actually demonstrates the current > behavior, although this is probably not correct. > As pointed out in the related mailing list thread [1], ALTER TABLE DROP > COLUMN likely suffers from the same issue. > 1. http://s.apache.org/LMT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
