[
https://issues.apache.org/jira/browse/PHOENIX-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15001577#comment-15001577
]
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_r44615400
--- Diff:
phoenix-core/src/it/java/org/apache/phoenix/execute/PartialCommitIT.java ---
@@ -259,10 +259,10 @@ private PhoenixConnection
getConnectionWithTableOrderPreservingMutationState() t
Connection con = driver.connect(url, new Properties());
PhoenixConnection phxCon = new
PhoenixConnection(con.unwrap(PhoenixConnection.class));
final
Map<TableRef,Map<ImmutableBytesPtr,MutationState.RowMutationState>> mutations =
Maps.newTreeMap(new TableRefComparator());
- return new PhoenixConnection(phxCon) {
+ return new PhoenixConnection(phxCon, null) {
--- End diff --
Probably a good idea to still have a PhoenixConnection(PhoenixConnection
conn) copy constructor that just calls the other one with a null second arg
(and put that in a separate pull request).
> 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)
