phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Jacoby (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4195) PHOENIX-4195 Deleting tenant rows using a tenant or global connection on the base table fails
Date Thu, 07 Jun 2018 23:16:00 GMT

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

Geoffrey Jacoby commented on PHOENIX-4195:
------------------------------------------

[~tdsilva] - I'd be wary of any change to this optimization that required a Scan, because
a Scan to avoid a Scan is probably counter-productive. 

How much does this optimization buy us normally? It skips needing to do a very short Scan
on the row key (usually one-row except in the cases that trigger the bug), but at the cost
of correctness problems. In most cases wouldn't that "just" be gaining ourselves a few milliseconds?

At least until we can include a PTable.hasChildViews() method that's part of the table header
row (perhaps as part of PHOENIX-3534?) the best solution might be just to disable this optimization. 

> 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
>            Assignee: Geoffrey Jacoby
>            Priority: Major
>         Attachments: test.diff
>
>
> The attached test fails.



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

Mime
View raw message