Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 535EA18A73 for ; Wed, 17 Feb 2016 19:14:22 +0000 (UTC) Received: (qmail 11347 invoked by uid 500); 17 Feb 2016 19:14:18 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 11224 invoked by uid 500); 17 Feb 2016 19:14:18 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 11185 invoked by uid 99); 17 Feb 2016 19:14:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Feb 2016 19:14:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 262E72C1F57 for ; Wed, 17 Feb 2016 19:14:18 +0000 (UTC) Date: Wed, 17 Feb 2016 19:14:18 +0000 (UTC) From: "Jonathan Hsieh (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-15283) Revert to IOException in TimeRange constructor to maintain API compat in 1.x line MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jonathan Hsieh created HBASE-15283: -------------------------------------- Summary: Revert to IOException in TimeRange constructor to maintain API compat in 1.x line Key: HBASE-15283 URL: https://issues.apache.org/jira/browse/HBASE-15283 Project: HBase Issue Type: Bug Reporter: Jonathan Hsieh >From the 1.2 rc3 conversation: [~busbey] {quote} * TimeRange's constructor with a min/max came in HBASE-14355. The constructor changed from IOException in the case of min > max to IllegalArgumentException. That's probably a more accurate exception, but it's a substantial source compat and behavior change for downstream. I've flagged the issue as incompatible and asked for a release note. For some reason the javadocs for TimeRange claim it's "for internal use only" so maybe it shouldn't have been IA.Public in the first place. {quote} Jon: {quote} A user could trigger the TimeRange constructed exception change by with the Get#setTimeRange/Scan#setTimeRange/Increment#setTimeRange apis. The signature in these classes don't change. (master [1], branch-1.2[2], tag 1.1.3[3]) Doing a little digging, it is worth noting that no public APIs take time range as an argument (HRegion, TimeRangeTracker do but they are private), however a few public metrics return it (Get, Scan, Increment). The comment also basically says don't use the constructor. {quote} [1]https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Get.java#L205 [2]https://github.com/apache/hbase/blob/branch-1.2/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Get.java#L195 [3] https://github.com/apache/hbase/blob/rel/1.1.3/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Get.java#L191 -- This message was sent by Atlassian JIRA (v6.3.4#6332)