[
https://issues.apache.org/jira/browse/HBASE-17394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796647#comment-15796647
]
huaxiang sun commented on HBASE-17394:
--------------------------------------
Update, the current logic is correct, for TimeRangeTracker, it is
[minimumTimestamp, maximumTimestamp], when it converts to TimeRange, the
TimeRange is also [minStamp, maxStamp]. I am going to update comments in the
code.
> 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)
