You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Geoffrey Jacoby (JIRA)" <ji...@apache.org> on 2015/12/15 23:52:46 UTC

[jira] [Created] (HBASE-14985) TimeRange constructors should set allTime when appropriate

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)