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

James Taylor updated PHOENIX-2577:
----------------------------------
    Attachment: PHOENIX-2577.patch

[~tdsilva] - please review.

> 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
>         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)

Reply via email to