phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas D'Silva (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4771) Deleting tenant rows using a global connection on the base table does not work.
Date Mon, 04 Jun 2018 22:50:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500985#comment-16500985
] 

Thomas D'Silva commented on PHOENIX-4771:
-----------------------------------------

This is related to [PHOENIX-4195|https://www.google.com/url?q=https://issues.apache.org/jira/browse/PHOENIX-4195&sa=D&source=hangouts&ust=1528238704241000&usg=AFQjCNFhWeb7m70aW_NP0ExcNDbr5Tc1rw].
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. 

> Deleting tenant rows using a global connection on the base table does not work.
> -------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4771
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4771
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Akshita Malhotra
>            Priority: Major
>         Attachments: deletes.diff
>
>
> Phoenix point deletes on base table using a global connection silently not deleting data
created by a tenant view.
> Ques 1: Is this the right behavior?
> Ques 2: If yes, should Phoenix validate and through an error/exception? If no, should
Phoenix delete the data correctly?
>  
> The attached test fails.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message