[
https://issues.apache.org/jira/browse/PHOENIX-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16436940#comment-16436940
]
Hudson commented on PHOENIX-4605:
---------------------------------
ABORTED: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #93 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.3/93/])
PHOENIX-4605 Support running multiple transaction providers (ammendment)
(jtaylor: rev e79228c4f35fafedd7a5c7ded0c053fc561846e7)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java
> Support running multiple transaction providers
> ----------------------------------------------
>
> Key: PHOENIX-4605
> URL: https://issues.apache.org/jira/browse/PHOENIX-4605
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: James Taylor
> Priority: Major
> Fix For: 4.14.0, 5.0.0
>
> Attachments: PHOENIX-4605_v1.patch, PHOENIX-4605_v2.patch,
> PHOENIX-4605_v3.patch, PHOENIX-4605_wip1.patch, PHOENIX-4605_wip2.patch,
> PHOENIX_4605_wip3.patch
>
>
> 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)
