You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2021/01/15 12:20:00 UTC
[jira] [Updated] (PHOENIX-6000) Client side DELETEs should use
local indexes for filtering
[ https://issues.apache.org/jira/browse/PHOENIX-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Istvan Toth updated PHOENIX-6000:
---------------------------------
Fix Version/s: (was: 5.0.1)
5.1.0
> Client side DELETEs should use local indexes for filtering
> ----------------------------------------------------------
>
> Key: PHOENIX-6000
> URL: https://issues.apache.org/jira/browse/PHOENIX-6000
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 4.15.0
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Priority: Major
> Fix For: 5.1.0, 4.16.0
>
> Attachments: 6000-4.x-HBase-1.5-v2.txt, 6000-4.x-HBase-1.5.txt, 6000-4.x-v3.txt, 6000-4.x-v4.txt
>
>
> I just noticed that client side DELETEs do not use local indexes for filtering if they do not cover all keys of all other indexes.
> Unless I am missing something this is not necessary, for local indexes we have the data available in the region and can fill back the uncovered column (just like we do for SELECTs)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)