You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Namit Jain (JIRA)" <ji...@apache.org> on 2013/01/14 17:04:13 UTC

[jira] [Commented] (HIVE-3833) object inspectors should be initialized based on partition metadata

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

Namit Jain commented on HIVE-3833:
----------------------------------

Refreshed, all the tests passed.

https://issues.apache.org/jira/secure/attachment/12564718/hive.3833.14.patch contains all the changes.

The phabricatr entry does not contain the changes for test results compiler files, since it was exceeding the limit.
                
> object inspectors should be initialized based on partition metadata
> -------------------------------------------------------------------
>
>                 Key: HIVE-3833
>                 URL: https://issues.apache.org/jira/browse/HIVE-3833
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Processor
>            Reporter: Namit Jain
>            Assignee: Namit Jain
>         Attachments: hive.3833.10.patch, hive.3833.11.patch, hive.3833.12.patch, hive.3833.13.patch, hive.3833.14.patch, hive.3833.1.patch, hive.3833.2.patch, hive.3833.3.patch, hive.3833.4.patch, hive.3833.5.patch, hive.3833.6.patch, hive.3833.7.patch, hive.3833.8.patch, hive.3833.9.patch
>
>
> Currently, different partitions can be picked up for the same input split based on the
> serdes' etc. And, we dont allow to change the schema for LazyColumnarBinarySerDe.
> Instead of that, different partitions should be part of the same split, only if the
> partition schemas exactly match. The operator tree object inspectors should be based
> on the partition schema. That would give greater flexibility and also help using binary serde with rcfile

--
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