[
https://issues.apache.org/jira/browse/PHOENIX-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364815#comment-16364815
]
James Taylor commented on PHOENIX-4605:
---------------------------------------
Yep, that’s more or less what I’m proposing. We’d need to potentially
initialize both transaction engines when we establish the connection to a
cluster, though. Or perhaps better would be to establish this lazily the first
time a transaction starts.
> 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)
