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

Sushanth Sowmyan updated HIVE-6432:
-----------------------------------

    Attachment: HIVE-6432.wip.1.patch

Now that 0.13 has forked out, and 0.14 is trunk, it's time for mass destruction!

I'm uploading a first attempt work-in-progress patch, which removes all 
org.apache.hcatalog entries. This is not backward-compatible, and removes the 
storage-handlers directory in hcat altogether.

I still need to remove deprecated functions and api points in various classes.

> Remove deprecated methods in HCatalog
> -------------------------------------
>
>                 Key: HIVE-6432
>                 URL: https://issues.apache.org/jira/browse/HIVE-6432
>             Project: Hive
>          Issue Type: Task
>          Components: HCatalog
>            Reporter: Sushanth Sowmyan
>            Assignee: Sushanth Sowmyan
>         Attachments: HIVE-6432.wip.1.patch
>
>
> There are a lot of methods in HCatalog that have been deprecated in HCatalog 
> 0.5, and some that were recently deprecated in Hive 0.11 (joint release with 
> HCatalog).
> The goal for HCatalog deprecation is that in general, after something has 
> been deprecated, it is expected to stay around for 2 releases, which means 
> hive-0.13 will be the last release to ship with all the methods that were 
> deprecated in hive-0.11 (the org.apache.hcatalog.* files should all be 
> removed afterwards), and it is also good for us to clean out and nuke all 
> other older deprecated methods.
> We should take this on early in a dev/release cycle to allow us time to 
> resolve all fallout, so I propose that we remove all HCatalog deprecated 
> methods after we branch out 0.13 and 0.14 becomes trunk.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to