[ 
https://issues.apache.org/jira/browse/HBASE-20065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16375989#comment-16375989
 ] 

Hudson commented on HBASE-20065:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #4645 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/4645/])
HBASE-20065 Revisit the timestamp usage in MetaTableAccessor (zhangduo: rev 
ba5fb53d147ef63415027f776928c478af37f515)
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestGetClosestAtOrBefore.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/master/assignment/RegionStateStore.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/favored/FavoredNodeAssignmentHelper.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/TestMetaTableAccessor.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/master/assignment/AssignmentManager.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/master/assignment/MockMasterServices.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsckRepair.java


> Revisit the timestamp usage in MetaTableAccessor
> ------------------------------------------------
>
>                 Key: HBASE-20065
>                 URL: https://issues.apache.org/jira/browse/HBASE-20065
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 2.0.0-beta-2
>
>         Attachments: HBASE-20065-v1.patch, HBASE-20065.patch
>
>
> It is totally a mess and makes me confusing when reimplementing the serial 
> replication feature. Let me do a clean up first.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to