[
https://issues.apache.org/jira/browse/PHOENIX-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508858#comment-16508858
]
James Taylor commented on PHOENIX-4195:
---------------------------------------
Probably best to file another Jira to talk about how a global tenant can best
see tenant specific view data. Since the schema is potentially different for
each view, doing so in a single query is going to be problematic. You could
have the same column in different views with different types.
As far as this Jira goes, you're going to break other functionality (i.e.
indexes on views) by mutating view data through a global connection. Also,
you'd be disabling an optimization that helps the vast majority of use cases. I
think it needs to be thought through more or a different approach needs to be
taken - like establishing a tenant specific connection to delete each tenant's
data. There's minuscule overhead in establishing this connection.
> 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)
