hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Jacoby (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-14985) TimeRange constructors should set allTime when appropriate
Date Tue, 15 Dec 2015 22:52:46 GMT
Geoffrey Jacoby created HBASE-14985:
---------------------------------------

             Summary: TimeRange constructors should set allTime when appropriate
                 Key: HBASE-14985
                 URL: https://issues.apache.org/jira/browse/HBASE-14985
             Project: HBase
          Issue Type: Improvement
    Affects Versions: 0.98.16.1, 1.1.2
            Reporter: Geoffrey Jacoby
            Assignee: Geoffrey Jacoby
            Priority: Minor


The default TimeRange constructor creates a range from 0 to Long.MAX_VALUE and sets an allTime
flag to true. This flag allows some performance optimizations when comparing or using TimeRanges.

This flag is not set, however, if you call "new TimeRange(0L)" or "new TimeRange(0L, Long.MAX_VALUE)",
even though both of these create a logically equivalent TimeRange to "new TimeRange()". Since
TimeRanges are immutable and detecting this condition is trivial, we should set the flag automatically
in the explicit constructors when appropriate. 




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

Mime
View raw message