Details
Description
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.
Attachments
Attachments
Issue Links
- duplicates
-
PHOENIX-4595 Add config option to disable server-side mutation processing
- Resolved
- is related to
-
PHOENIX-5044 Remove server side mutation code from Phoenix
- Open
- relates to
-
PHOENIX-5007 DELETE FROM times out - even with large HBase timeout setting
- Open