You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2018/11/22 03:42:00 UTC

[jira] [Updated] (PHOENIX-5026) Add client setting to disable server side mutations

     [ https://issues.apache.org/jira/browse/PHOENIX-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lars Hofhansl updated PHOENIX-5026:
-----------------------------------
    Summary: Add client setting to disable server side mutations  (was: Add client setting to disable server side deletes)

> Add client setting to disable server side mutations
> ---------------------------------------------------
>
>                 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)