[
https://issues.apache.org/jira/browse/PHOENIX-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363286#comment-16363286
]
Akshita Malhotra commented on PHOENIX-4344:
-------------------------------------------
[~jamestaylor] Can you explain why would it do a point scan? Maybe I am
thinking in the wrong direction but as [~gjacoby] explained, even if the
initial delete is deleting over a non PK column, when a point phoenix delete
query is being issued, I can provide the PK information (obtain from the map
reduce scan) along with the extra predicate that would include the non-PK
column.
> MapReduce Delete Support
> ------------------------
>
> Key: PHOENIX-4344
> URL: https://issues.apache.org/jira/browse/PHOENIX-4344
> Project: Phoenix
> Issue Type: New Feature
> Affects Versions: 4.12.0
> Reporter: Geoffrey Jacoby
> Assignee: Geoffrey Jacoby
> Priority: Major
>
> Phoenix already has the ability to use MapReduce for asynchronous handling of
> long-running SELECTs. It would be really useful to have this capability for
> long-running DELETEs, particularly of tables with indexes where using HBase's
> own MapReduce integration would be prohibitively complicated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
