[
https://issues.apache.org/jira/browse/PHOENIX-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510336#comment-16510336
]
Thomas D'Silva commented on PHOENIX-4195:
-----------------------------------------
I think we have to disable all mutations using a global connection to any table
that has child views.
The tenant or global connection would have to create the view first and then
create the view index. Once the view is created whenever the base table is
resolved (by making a call to the server) to fetch the latest metadata the
basetable PTable would have the hasChildViews flag set to true.
Index creation should be able to handle any in-progress mutations queued on the
region because we run a second index population catch up query. See
PHOENIX-2582 on details of how to improve this.
We need the hasChildViews to prevent issues while creating global views on non
multi-tenant tables.
> PHOENIX-4195 Deleting view rows with extended PKs through the base table
> silently fails
> ---------------------------------------------------------------------------------------
>
> Key: PHOENIX-4195
> URL: https://issues.apache.org/jira/browse/PHOENIX-4195
> Project: Phoenix
> Issue Type: Bug
> Reporter: Thomas D'Silva
> Assignee: Geoffrey Jacoby
> Priority: Major
> Attachments: test.diff
>
>
> The attached test fails.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
