[
https://issues.apache.org/jira/browse/PHOENIX-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15340203#comment-15340203
]
Ankit Singhal commented on PHOENIX-2999:
----------------------------------------
[~samarthjain], sure,I'll update the workaround after testing it.
[~jamestaylor], I missed the handling for multi-tenant table in UpgradeUtil
while upgrading existing table to namespace, Actually , current implementation
is taking only global (not all the tenant) views to update link of physical
table and indexes.
bq. Only the physical table would have a namespace associated with it, right?
Yes
bq. Views and indexes of multi-tenant tables should all be in the same
namespace as the physical table
No, only indexes needs to be in same namespace/schema as parent table. Views
can be created with different schema(say A.V) than physical table(say B.P) and
so the index created on view (A.V) will reside in the parent table schema (A)
only.
> Upgrading Multi-tenant table to map with namespace using upgradeUtil
> --------------------------------------------------------------------
>
> Key: PHOENIX-2999
> URL: https://issues.apache.org/jira/browse/PHOENIX-2999
> Project: Phoenix
> Issue Type: Bug
> Reporter: Ankit Singhal
> Assignee: Ankit Singhal
>
> currently upgradeUtil doesn't handle multi-tenant table with tenant views
> properly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
