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/07 03:59:39 UTC

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

James Taylor created PHOENIX-2577:
-------------------------------------

             Summary: 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


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)