[
https://issues.apache.org/jira/browse/PHOENIX-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16236856#comment-16236856
]
James Taylor commented on PHOENIX-4344:
---------------------------------------
I'd go with Option #2. Option #1 will be problematic for tables with indexes on
non pk columns. If you can tack on the correct RVC (or perhaps did below the
Phoenix API and set the start/stop row of the Scan) based on the info in the
QueryPlan, then the delete logic will all be handled completely by
DeleteCompiler. You just need to grab the mutations using
PhoenixRuntime.getUncommittedDataIterator(). You might just use
FormatToBytesWritableMapper for inspiration/code borrowing.
> 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
(v6.4.14#64029)
