[
https://issues.apache.org/jira/browse/PHOENIX-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16690107#comment-16690107
]
Lars Hofhansl edited comment on PHOENIX-5026 at 11/16/18 10:59 PM:
-------------------------------------------------------------------
And some tests - in fact just parameterized the existing tests.
Note that I had to turn off {{testUpsertSelectDoesntSeeUpsertedData}} when
allowServerSideMutations is false. It seems when splits happen then restarted
upserts *can* see their own data. I need to reason about whether this is
expected or not.
was (Author: lhofhansl):
And some tests - in fact just parameterized the existing tests.
> 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
> Attachments: 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)
