[
https://issues.apache.org/jira/browse/PHOENIX-5524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950728#comment-16950728
]
Chinmay Kulkarni commented on PHOENIX-5524:
-------------------------------------------
[~gjacoby] PHOENIX-4983 already disallows doing this for "transactional tables
or mutable tables with indexes.." etc. so is this fix as easy as extending the
check for ANY table (including immutable) that has an index? If so, the fix
should be straightforward, otherwise, as Lars said, is it okay to push this to
4.15.1?
> 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)
