hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sahil Takiar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-17130) Add automated tests to check backwards compatibility of core APIs
Date Thu, 20 Jul 2017 18:08:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-17130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095130#comment-16095130
] 

Sahil Takiar commented on HIVE-17130:
-------------------------------------

Here are the relevant JIRAs from other Apache Projects who have done similar things:

HADOOP-13583
HBASE-12808 and HBASE-18020
KUDU-1265

> 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: Test
>            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)

Mime
View raw message