phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-1674) Snapshot isolation transaction support through Tephra
Date Fri, 20 Nov 2015 01:24:11 GMT


ASF GitHub Bot commented on PHOENIX-1674:

Github user JamesRTaylor commented on a diff in the pull request:
    --- Diff: phoenix-core/src/it/java/org/apache/phoenix/end2end/index/ ---
    @@ -45,19 +45,24 @@
     	private final boolean localIndex;
     	private final String tableDDLOptions;
    --- End diff --
    Instead of using System.currentMillis() in the table name (which will create a new physical
table for every test), can you create a TestUtil.getTableName(String prefix, boolean localIndex,
boolean mutable, boolean transactional, Integer saltBuckets) and creates a sensible table

> Snapshot isolation transaction support through Tephra
> -----------------------------------------------------
>                 Key: PHOENIX-1674
>                 URL:
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: James Taylor
>              Labels: SFDC
> Tephra ( and 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

View raw message