You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Geoffrey Jacoby (JIRA)" <ji...@apache.org> on 2017/06/08 19:41:18 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=16043297#comment-16043297 ]
Geoffrey Jacoby commented on PHOENIX-3925:
------------------------------------------
We should probably also make the language on the website stronger. Right now it says it's "supported" but "not recommended", as opposed to the other limitations which say the stronger "may not". For 4.11 and up Phoenix will enforce, but it would be good for users of older versions using the docs to get more clarity too.
> 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
> Fix For: 4.11.0
>
>
> 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
(v6.3.15#6346)