[
https://issues.apache.org/jira/browse/PHOENIX-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15001588#comment-15001588
]
ASF GitHub Bot commented on PHOENIX-1674:
-----------------------------------------
Github user JamesRTaylor commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/126#discussion_r44615771
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/compile/StatementPlan.java ---
@@ -29,4 +33,6 @@
ParameterMetaData getParameterMetaData();
ExplainPlan getExplainPlan() throws SQLException;
+ public Set<TableRef> getSourceRefs();
--- End diff --
This interface change (along with the one in MutationPlan) caused some
diffs not related to transactions. If it's easy to merge that back separately,
that might help reduce the extraneous, non transactional changes.
> Snapshot isolation transaction support through Tephra
> -----------------------------------------------------
>
> Key: PHOENIX-1674
> URL: https://issues.apache.org/jira/browse/PHOENIX-1674
> Project: Phoenix
> Issue Type: Improvement
> Reporter: James Taylor
> Labels: SFDC
>
> Tephra (http://tephra.io/ and https://github.com/caskdata/tephra) is one
> option for getting transaction support in Phoenix. Let's use this JIRA to
> discuss the way in which this could be integrated along with the pros and
> cons.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
