hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sushanth Sowmyan (JIRA)" <>
Subject [jira] [Commented] (HIVE-4896) create binary backwards compatibility layer hcatalog 0.12 and 0.11
Date Thu, 05 Sep 2013 21:17:52 GMT


Sushanth Sowmyan commented on HIVE-4896:

Regd 4896.remove_Exim_add_011_src_test :

  * verified that there are no diffs with 0.11 code
  * webhcat svr code was moved as part of HIVE-4895 and not restored to old package names
- but this is okay, since webhcat svr is a standalone server, and if someone is using an old
release, they have the old package, and this causes no compatibility problems
  * e2e test utils were moved and not restored. Again, not a problem, they're purely tests
that are run manually, and causes no compatibility problems.
  * hbase hcat storage handler was moved and not restored. This is a problem, since we're
deprecating hbase hcat storage handler - if anything, this is a case where moving was not
necessary, but we do need to retain the old package names for backward compatibility.
> create binary backwards compatibility layer hcatalog 0.12 and 0.11
> ------------------------------------------------------------------
>                 Key: HIVE-4896
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: HCatalog
>    Affects Versions: 0.12.0
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>             Fix For: 0.12.0
>         Attachments: 4896.add_deprecation, 4896.fix_shim_layer, 4896.remove_Exim_add_011_src_test,
>   Original Estimate: 72h
>  Remaining Estimate: 72h
> 1. create a 011 dir in each HCat submodule to hold these classes
> 2. update build to place these classes into jars
> 3. figure out how to test this
> The goal is for users who were using public API (e.g. HCatLoader) in their programs to
be able to upgrade to hive 0.12 and have their programs still work without change.
> The compatibility layer will have a sunset clause to be removed in 2 releases.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message