[
https://issues.apache.org/jira/browse/PHOENIX-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16695524#comment-16695524
]
Lars Hofhansl commented on PHOENIX-5026:
----------------------------------------
OK... I'll commit this today. It's purely additional, defaults to the current
behaviors, and even with server mutations are disabled the behavior does not
change (that I know off).
> 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
> Affects Versions: 4.15.0, 4.14.1
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Priority: Major
> Attachments: 5026-withtests-v2.txt, 5026-withtests.txt, 5026.txt
>
>
> 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)
