[
https://issues.apache.org/jira/browse/PHOENIX-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16665700#comment-16665700
]
Geoffrey Jacoby commented on PHOENIX-4344:
------------------------------------------
[~lhofhansl] - true, but it depends on your definition of "client". If your
usual "client" is a web server running the thick client, and your YARN cluster
is co-located with your HBase "server-side", the execution will effectively be
server-side, though not actually within the server process itself. (Even though
yes, there may be server-to-server hops involved because YARN will try to place
the mappers near the _base table,_ but also have to cleanup the indexes which
are likely not on the same region server).
It's much the same as using PQS.
> 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)
