hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-6432) Remove deprecated methods in HCatalog
Date Sat, 15 Mar 2014 06:25:43 GMT

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

Ashutosh Chauhan updated HIVE-6432:
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.14.0
           Status: Resolved  (was: Patch Available)

Committed to trunk. Thanks, Sushanth!

> Remove deprecated methods in HCatalog
> -------------------------------------
>
>                 Key: HIVE-6432
>                 URL: https://issues.apache.org/jira/browse/HIVE-6432
>             Project: Hive
>          Issue Type: Task
>          Components: HCatalog
>    Affects Versions: 0.14.0
>            Reporter: Sushanth Sowmyan
>            Assignee: Sushanth Sowmyan
>             Fix For: 0.14.0
>
>         Attachments: HIVE-6432.patch, HIVE-6432.wip.1.patch, HIVE-6432.wip.2.patch, hcat.6432.test.out
>
>
> 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)

Mime
View raw message