[
https://issues.apache.org/jira/browse/PHOENIX-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15001575#comment-15001575
]
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_r44615251
--- Diff:
phoenix-core/src/it/java/org/apache/phoenix/end2end/index/IndexMetadataIT.java
---
@@ -100,7 +100,7 @@ private static void assertActiveIndex(Connection conn,
String schemaName, String
String fullTableName = SchemaUtil.getTableName(schemaName,
tableName);
conn.createStatement().executeQuery("SELECT count(*) FROM " +
fullTableName).next(); // client side cache will update
PhoenixConnection pconn = conn.unwrap(PhoenixConnection.class);
- pconn.getMetaDataCache().getTable(new
PTableKey(pconn.getTenantId(), fullTableName)).getIndexMaintainers(ptr, pconn);
--- End diff --
Probably good to factor out this method change (i.e. having
PhoenixConnection.getTable()) into a separate pull to master as it appears to
have generated a lot of diffs unrelated to transactions.
> 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)
