You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Eugene Koifman (JIRA)" <ji...@apache.org> on 2014/02/15 01:42:21 UTC
[jira] [Commented] (HIVE-6432) Remove deprecated methods in
HCatalog
[ https://issues.apache.org/jira/browse/HIVE-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13902210#comment-13902210 ]
Eugene Koifman commented on HIVE-6432:
--------------------------------------
+1 on the idea. we'll also be able to remove a may of unit tests that cover old API
> 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
>
> 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.1.5#6160)