You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sahil Takiar (JIRA)" <ji...@apache.org> on 2017/07/19 22:15:00 UTC

[jira] [Assigned] (HIVE-17130) Add automated tests to check backwards compatibility of core APIs

     [ https://issues.apache.org/jira/browse/HIVE-17130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sahil Takiar reassigned HIVE-17130:
-----------------------------------


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