[
https://issues.apache.org/jira/browse/PHOENIX-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364534#comment-16364534
]
Geoffrey Jacoby commented on PHOENIX-4605:
------------------------------------------
[~jamestaylor] - could there be a table-level override of the global
hbase-site.xml setting, with a validation check to make sure that tables from
two different TALs can't participate in a transaction with each other? That
would allow you to have a global setting of "Tephra", but experiment with Omid
on new tables.
> Add TRANSACTION_PROVIDER and DEFAULT_TRANSACTION_PROVIDER instead of using
> boolean
> ----------------------------------------------------------------------------------
>
> Key: PHOENIX-4605
> URL: https://issues.apache.org/jira/browse/PHOENIX-4605
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Priority: Major
>
> We should deprecate QueryServices.DEFAULT_TABLE_ISTRANSACTIONAL_ATTRIB and
> instead have a QueryServices.DEFAULT_TRANSACTION_PROVIDER now that we'll have
> two transaction providers: Tephra and Omid. Along the same lines, we should
> add a TRANSACTION_PROVIDER column to SYSTEM.CATALOG and stop using the
> IS_TRANSACTIONAL table property. For backwards compatibility, we can assume
> the provider is Tephra if the existing properties are set to true.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
