[jira] [Resolved] (PHOENIX-623) Upgrade script for SYSTEM.TABLE changes to support multitenant tables

["Gabriel Reid (JIRA)" <ji...@apache.org>]

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

Gabriel Reid resolved PHOENIX-623.
----------------------------------

    Resolution: Fixed

Bulk resolve of closed issues imported from GitHub. This status was reached by first re-opening all closed imported issues and then resolving them in bulk.

> Upgrade script for SYSTEM.TABLE changes to support multitenant tables
> ---------------------------------------------------------------------
>
>                 Key: PHOENIX-623
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-623
>             Project: Phoenix
>          Issue Type: Task
>    Affects Versions: 3.0-Release
>            Reporter: elevine
>            Assignee: James Taylor
>
> Two modifications to SYSTEM.TABLE for multitenant tables:
> 1. TENANT_ID leading PK column
> 2. TYPE_ID non-PK column will be added for issue -452
> From @jamestaylor: Adding the TENANT_ID column cannot be performed via ALTER TABLE (you can only do that with nullable columns at end of rowkey).  Look at SchemaUtil.upgradeTo2IfNecessary and how/when it's called. You'll need to do a "raw" scan like that so that you don't miss updating everything. For SYSTEM.TABLE upgrades, we do it automatically on first connection to the cluster. You can mimic pretty closely what we do for other upgrade-related stuff.



--
This message was sent by Atlassian JIRA
(v6.2#6252)