[HBASE-22841] TimeRange's factory functions do not support ranges, only `allTime` and `at`

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0, 2.1.5
• Fix Version/s: 3.0.0-alpha-1, 2.3.0, 2.0.6, 2.2.1, 2.1.6
• Component/s: Client
• Hadoop Flags: Reviewed

Release Note

Add serveral API in TimeRange class for avoiding using the deprecated TimeRange constructor:
* TimeRange#from: Represents the time interval [minStamp, Long.MAX_VALUE)
* TimeRange#until: Represents the time interval [0, maxStamp)
* TimeRange#between: Represents the time interval [minStamp, maxStamp)

• Assignee: Huon Wilson
• Reporter: Huon Wilson
• Created: 13/Aug/19 05:02
• Updated: 19/Aug/19 01:48
• Resolved: 17/Aug/19 02:35

Description

The org.apache.hadoop.hbase.io.TimeRange is used in functions like org.apache.hadoop.hbase.client.Table.CheckAndMutateBuilder#timeRange.

The current ways to create a TimeRange are:

• factory functions: at (a single instant), allTime (all valid timestamps)
• deprecated and @InterfaceAudience.Private constructors, which support more ranges, like [minStamp, maxStamp), and [minStamp, MAX)

This is insufficient for all but the simplest use of the CheckAndMutateBuilder#timeRange function.

On [e-mail], it was suggested that more factory functions could be added: https://lists.apache.org/thread.html/0ffc5e57c396873d56e49d7b02e823432b053fb98037ee6778d7c2ce@%3Cuser.hbase.apache.org%3E

However, TimeRange's documentation currently says:

 * Can be returned and read by clients.  Should not be directly created by clients.
 * Thus, all constructors are purposely @InterfaceAudience.Private.

so another approach to making CheckAndMutateBuilder#timeRange useful may be required.

Issue Links

• is related to: HBASE-22795 Align the API interfaces in TimeRange
• links to: GitHub Pull Request #483