[
https://issues.apache.org/jira/browse/PHOENIX-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-4096:
----------------------------------
Attachment: PHOENIX-4096_wip1.patch
Patch that enforces that CURRENT_SCN may only be used in a read-only manner.
Currently setting UpsertValuesIT and UpsertSelectIT to abstract while they're
not yet converted.
> Disallow DML operations on connections with CURRENT_SCN set
> -----------------------------------------------------------
>
> Key: PHOENIX-4096
> URL: https://issues.apache.org/jira/browse/PHOENIX-4096
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: James Taylor
> Fix For: 4.12.0
>
> Attachments: PHOENIX-4096_wip1.patch, PHOENIX-4096_wip.patch
>
>
> We should make a connection read-only if CURRENT_SCN is set. It's really a
> bad idea to go back in time and update data and it won't work with secondary
> indexing, potentially leading to your index and table getting out of sync.
> For testing purposes, where we need to control the timestamp, we should rely
> on the EnvironmentEdgeManager instead to control the current time.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
