[
https://issues.apache.org/jira/browse/PHOENIX-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16502168#comment-16502168
]
Geoffrey Jacoby commented on PHOENIX-4195:
------------------------------------------
[~tdsilva] - on PHOENIX-4771 you mentioned that "The PK of the base table
consists of (TENANT_ID, K). The delete over the base table specifies both these
columns so Phoenix thinks you are deleting a single row. The fix is to not do
this optimization for multi-tenant tables."
If you can point us to where that incorrect optimization is, perhaps
[~akshita.malhotra] or I could take care of fixing it, if splittable
System.Catalog is still taking all your bandwidth. I tried taking a look at
DeleteCompiler yesterday but couldn't find it.
> PHOENIX-4195 Deleting tenant rows using a tenant or global connection on the
> base table fails
> ---------------------------------------------------------------------------------------------
>
> Key: PHOENIX-4195
> URL: https://issues.apache.org/jira/browse/PHOENIX-4195
> Project: Phoenix
> Issue Type: Bug
> Reporter: Thomas D'Silva
> Priority: Major
> Attachments: test.diff
>
>
> The attached test fails.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
