[
https://issues.apache.org/jira/browse/PHOENIX-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689848#comment-16689848
]
Geoffrey Jacoby commented on PHOENIX-5026:
------------------------------------------
Won't that require pull lots of data back to the client?
As a side note, client side deletes have some "funny" behavior too -- see
PHOENIX-4195 for an existing client-side optimization that can lead to
incorrect results.
> Add client setting to disable server side deletes
> -------------------------------------------------
>
> Key: PHOENIX-5026
> URL: https://issues.apache.org/jira/browse/PHOENIX-5026
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Lars Hofhansl
> Priority: Major
>
> Like PHOENIX-3818 server side deletes.
> We've seen issues with larger deletes (see PHOENIX-5007).
> In many case it is probably better to handle deletes from the client. That
> way requests are properly chunked, handler threads are not tied up, and
> there's no "funniness" with issues mutation from a scan RPC.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
