[
https://issues.apache.org/jira/browse/PHOENIX-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16695602#comment-16695602
]
Lars Hofhansl commented on PHOENIX-5026:
----------------------------------------
Hmm...
{code}
Error Message
ERROR 1200 (42Z00): Sequence already exists. tableName=KEYS
Stacktrace
org.apache.phoenix.schema.SequenceAlreadyExistsException: ERROR 1200 (42Z00):
Sequence already exists. tableName=KEYS
at
org.apache.phoenix.end2end.UpsertSelectAutoCommitIT.testUpsertSelectDoesntSeeUpsertedData(UpsertSelectAutoCommitIT.java:178)
{code}
Needs a test-only addendum.
> 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
> Fix For: 4.15.0, 4.14.2
>
> 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)
