[
https://issues.apache.org/jira/browse/PHOENIX-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112825#comment-14112825
]
James Taylor commented on PHOENIX-1208:
---------------------------------------
We already have a split policy that prevents splits i the middle of a tenant's
metadata. We haven't seen it split, but it could if there are many, many
tenants. This is the only case where we need to check across multiple tenants.
> Check for existence of views doesn't take into account the fact that
> SYSTEM.CATALOG could be split across regions
> -----------------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-1208
> URL: https://issues.apache.org/jira/browse/PHOENIX-1208
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 3.1, 4.1
> Reporter: Jan Fernando
> Priority: Minor
> Attachments: PHOENIX-1208.patch
>
>
> It is possible that when SYSTEM.CATALOG gets very large that it will be split
> across multiple regions. The parent table metadata is guaranteed via
> MetaDataSplitPolicy to be in the same region. However, child tenant specific
> views could end split across multiple regions. The hasViews() method, when
> checking for the existence of any views, scans only the region the parent
> table metadata is located in. We should detect whether the views span
> multiple regions and scan across them all.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
