phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-5026) Add client setting to disable server side mutations
Date Thu, 22 Nov 2018 04:33:00 GMT

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

Lars Hofhansl updated PHOENIX-5026:
-----------------------------------
    Comment: was deleted

(was: Stupid question... Are the 4.x-HBase-1.1 and 4.x-HBase-0.98 branches still active?
Their commit history seems to be quite different.)

> 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)

Mime
View raw message