[jira] [Resolved] (PHOENIX-4595) Add config option to disable server-side mutation processing

["Thomas D'Silva (JIRA)" <ji...@apache.org>]

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

Thomas D'Silva resolved PHOENIX-4595.
-------------------------------------
    Resolution: Duplicate

> Add config option to disable server-side mutation processing
> ------------------------------------------------------------
>
>                 Key: PHOENIX-4595
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4595
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: James Taylor
>            Priority: Major
>
> Phoenix has an option to process a DELETE or an UPSERT SELECT to the same table purely on the server side. Though this prevents the need to return the row keys back to the client (reducing network traffic), it can also lead to the handler being tied up for a long period of time:
> - if many mutations are being processed
> - if the table has mutable indexes and the update to them fail (since the retry will happen on the server side).
> We should provide a default to disable this optimization.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)