Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Wed, 19 Jul 2017 22:15:00 +0000 (UTC)
From: "Sahil Takiar (JIRA)" <jira@apache.org>
To: dev@hive.apache.org
Message-ID: <JIRA.13088577.1500502456000.286824.1500502500085@Atlassian.JIRA>
In-Reply-To: <JIRA.13088577.1500502456000@Atlassian.JIRA>
References: <JIRA.13088577.1500502456000@Atlassian.JIRA> <JIRA.13088577.1500502456098@jira-lw-us.apache.org>
Subject: [jira] [Created] (HIVE-17130) Add automated tests to check
 backwards compatibility of core APIs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 19 Jul 2017 22:15:04 -0000

Sahil Takiar created HIVE-17130:
-----------------------------------

             Summary: Add automated tests to check backwards compatibility of core APIs
                 Key: HIVE-17130
                 URL: https://issues.apache.org/jira/browse/HIVE-17130
             Project: Hive
          Issue Type: Bug
            Reporter: Sahil Takiar
            Assignee: Sahil Takiar


We should added automated tests that check we are not adding backwards incompatible changes to core APIs (e.g. HMS APIs, SerDe APIs, UDF APIs, etc.).

Other Apache components, such as HBase and Hadoop already have existing checks. They are largely based on the japi-compliance-checker: https://lvc.github.io/japi-compliance-checker/

The nice thing about the japi-compliance-checker is that it can identify an interface as "any class with a specified Java annotation", so we can use the compliance-checker to check for backwards compatibility of any classes annotated with InterfaceAudience.Public

Ideally, we can build this check into our pre-commit job, or get it into YETUS, since we are already working on adding YETUS support to Hive.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)