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 2013/08/29 21:20:51 UTC

[jira] [Commented] (HIVE-4896) create binary backwards compatibility layer hcatalog 0.12 and 0.11

    [ https://issues.apache.org/jira/browse/HIVE-4896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753954#comment-13753954 ] 

Eugene Koifman commented on HIVE-4896:
--------------------------------------

with core and hcatalog-pig-adapter under org.apache.hcatalog brought from 0.11 1 test fails:

TestSemanticAnalysis#testAddReplaceCols()
	Failure	expected:<0> but was:<1> 

junit.framework.AssertionFailedError: expected:<0> but was:<1>
at org.apache.hcatalog.cli.TestSemanticAnalysis.testAddReplaceCols(TestSemanticAnalysis.java:212)

The reason is that for RCFILE the default in 0.12 is LazyBinaryColumnarSerDe (hive.default.rcfile.serde) which doesn't allow updating columns.  
                
> create binary backwards compatibility layer hcatalog 0.12 and 0.11
> ------------------------------------------------------------------
>
>                 Key: HIVE-4896
>                 URL: https://issues.apache.org/jira/browse/HIVE-4896
>             Project: Hive
>          Issue Type: Sub-task
>          Components: HCatalog
>    Affects Versions: 0.12.0
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>             Fix For: 0.12.0
>
>   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: http://www.atlassian.com/software/jira