[
https://issues.apache.org/jira/browse/PHOENIX-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15090276#comment-15090276
]
Hudson commented on PHOENIX-2577:
---------------------------------
SUCCESS: Integrated in Phoenix-master #1059 (See
[https://builds.apache.org/job/Phoenix-master/1059/])
PHOENIX-2577 Use same timestamp technique for alter table as create
(jamestaylor: rev 55c5be2000d7ee3042a6c971e30cff6cb0dfb301)
*
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/MetaDataEndpointImpl.java
* phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java
> 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)
