phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Araujo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3818) Add client setting to disable server side UPSERT SELECT work
Date Wed, 03 May 2017 16:04:04 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995135#comment-15995135
] 

Alex Araujo commented on PHOENIX-3818:
--------------------------------------

Thanks for the feedback [~jamestaylor]. v2 enables new PHOENIX-3271 behavior by default. If
the new property is set to false, UPSERT SELECT work for the same table will still be performed
on the server.

Moved isPkPositionChanging() from UngroupedAggregateRegionObserver to ExpressionUtil to detect
if PK columns are changing in UpsertCompiler. PHOENIX-3271 allows RS -> RS calls when PK
columns are changing. This is still the default behavior. When the new property is false,
the work is done on the client.

The new feature toggle may be useful for users that do UPSERT SELECTs but do not have the
server side settings for RS->RS RPC priority.

> Add client setting to disable server side UPSERT SELECT work
> ------------------------------------------------------------
>
>                 Key: PHOENIX-3818
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3818
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 4.10.0
>            Reporter: Alex Araujo
>            Assignee: Alex Araujo
>         Attachments: PHOENIX-3818.v1.patch, PHOENIX-3818.v2.patch
>
>
> PHOENIX-3271 introduced RS -> RS RPCs by default via UPSERT SELECT statements. Add
a client side setting that disables this behavior.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message