You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@phoenix.apache.org by "Lars Hofhansl (Jira)" <ji...@apache.org> on 2019/10/12 21:08:00 UTC

[jira] [Commented] (PHOENIX-5524) Connections with SCN should fail mutations on tables with any index

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

Lars Hofhansl commented on PHOENIX-5524:
----------------------------------------

That's a pretty harsh limitation. Can we limit this to only table with the new index design. I.e. not local indexes (and I'm not sure what should happen with transactional indexes - that use Omid or Tephra).

> Connections with SCN should fail mutations on tables with any index
> -------------------------------------------------------------------
>
>                 Key: PHOENIX-5524
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5524
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.15.0, 5.1.0
>            Reporter: Priyank Porwal
>            Priority: Major
>             Fix For: 4.15.0, 5.1.0
>
>
> PHOENIX-4983 allowed mutations on subset of tables for connections using SCN.
> We need to forbid mutations on tables with any index so that they do not conflict with assumptions made by consistent secondary indexing redesign.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)