You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Swaroopa Kadam (JIRA)" <ji...@apache.org> on 2018/12/14 16:15:00 UTC
[jira] [Updated] (PHOENIX-4983) Allow using a connection with a SCN
set to write data to tables EXCEPT transactional tables or mutable tables
with indexes or tables with a ROW_TIMESTAMP column
[ https://issues.apache.org/jira/browse/PHOENIX-4983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Swaroopa Kadam updated PHOENIX-4983:
------------------------------------
Attachment: (was: PHOENIX-4983-missing-header.patch)
> Allow using a connection with a SCN set to write data to tables EXCEPT transactional tables or mutable tables with indexes or tables with a ROW_TIMESTAMP column
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-4983
> URL: https://issues.apache.org/jira/browse/PHOENIX-4983
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Thomas D'Silva
> Assignee: Swaroopa Kadam
> Priority: Major
> Labels: SFDC
> Fix For: 4.15.0, 5.1.0
>
> Attachments: PHOENIX-4983-4.x-HBase-1.4.patch, PHOENIX-4983-4.x-HBase-1.4.patch, PHOENIX-4983-4.x-HBase-1.4.patch, PHOENIX-4983-4.x-HBase-1.4.patch, PHOENIX-4983-missing-header.patch
>
>
> Currently If a SCN is set on a connection it is read-only. We only need to prevent a client from using a connection with a SCN set to upsert data for:
> 1) transactional tables
> 2) mutable tables with indexes
> 3) tables with a ROW_TIMESTAMP column
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)