hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "huaxiang sun (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17394) Correct TimeRangeTracker#init() logic
Date Fri, 30 Dec 2016 01:15:58 GMT

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

huaxiang sun commented on HBASE-17394:
--------------------------------------

Forgot to mention that the logic there needs to be corrected accordingly, given that it is

[minimumTimestamp, maximumTimestamp)

https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/TimeRangeTracker.java#L116



> Correct TimeRangeTracker#init() logic
> -------------------------------------
>
>                 Key: HBASE-17394
>                 URL: https://issues.apache.org/jira/browse/HBASE-17394
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>            Reporter: huaxiang sun
>            Assignee: huaxiang sun
>            Priority: Minor
>
> It is supposed to be [minimumTimestamp, maximumTimestamp), the following logic suggests
 [minimumTimestamp, maximumTimestamp]
> https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/TimeRangeTracker.java#L81
> needs to be modified to set(l, l + 1)



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

Mime
View raw message