You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Vincent Poon (JIRA)" <ji...@apache.org> on 2018/10/09 20:22:00 UTC

[jira] [Commented] (PHOENIX-3925) Disallow usage of ON DUPLICATE KEY clause on tables with global secondary indexes

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

Vincent Poon commented on PHOENIX-3925:
---------------------------------------

Updated website documentation to this:
"Global indexes on columns being atomically updated are not supported, as potentially a separate RPC across the wire would be made while the row is under lock to maintain the secondary index."

> Disallow usage of ON DUPLICATE KEY clause on tables with global secondary indexes
> ---------------------------------------------------------------------------------
>
>                 Key: PHOENIX-3925
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3925
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>            Priority: Major
>             Fix For: 4.11.0
>
>         Attachments: PHOENIX-3925.patch
>
>
> For the reasons of service protection, rather than just documenting that you shouldn't use the ON DUPLICATE KEY clause on tables with global secondary indexes, we should instead throw an exception if this is attempted. See reasons listed here for the reason: https://phoenix.apache.org/atomic_upsert.html#Limitations



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