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 Sat, 14 Nov 2015 00:57:11 GMT


ASF GitHub Bot commented on PHOENIX-1674:

Github user JamesRTaylor commented on a diff in the pull request:
    --- Diff: phoenix-core/src/main/java/org/apache/phoenix/jdbc/ ---
    @@ -450,7 +463,7 @@ private void closeStatements() throws SQLException {
             // from modifying this list.
             this.statements = Lists.newArrayList();
             try {
    -            mutationState.rollback(this);
    +            mutationState.clear();
    --- End diff --
    I'm pretty sure we want to call mutationState.rollback() here instead of mutationState.clear().
Add a test like this to confirm:
    - upsert a few rows to a transactional table
    - query the table (which will write you upserts but not commit them)
    - close the connection
    I think the writes will get left hanging and once the tx times out, I'm not sure what'll
happen. The txID may end up on the invalid list (which is not great) or not (which is even

> 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