You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/01/08 23:36:40 UTC

[jira] [Resolved] (PHOENIX-2577) Use same timestamp technique for alter table as create table

     [ https://issues.apache.org/jira/browse/PHOENIX-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Taylor resolved PHOENIX-2577.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 4.7.0

> Use same timestamp technique for alter table as create table
> ------------------------------------------------------------
>
>                 Key: PHOENIX-2577
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2577
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 4.7.0
>
>         Attachments: PHOENIX-2577.patch
>
>
> We currently burn a commit when we do DDL and use the read pointer as our timestamp for our system catalog (so that we're reading at the same timestamp we're writing). We should be consistent about this and do the same for alter table. This will hopefully fix some test flakiness in the TransactionIT.testNoConflictDetectionForImmutableRows test.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)