You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Gunther Hagleitner (JIRA)" <ji...@apache.org> on 2014/05/23 07:40:02 UTC

[jira] [Commented] (HIVE-7113) Support fully managed partitioned table, which does not allow partitions to have different properties with table

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

Gunther Hagleitner commented on HIVE-7113:
------------------------------------------

Are you failing "alter table" statements on a fully managed table? Or are you removing the property as soon as the schema changes?

I've been bitten by the cost of fetching too many partitions before, but schema evolution is typically important on tables with many partitions. Any chance you looked at some sort of de-duping partition information before sending it over thrift? Is it very expensive/difficult to do that?

> Support fully managed partitioned table, which does not allow partitions to have different properties with table
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-7113
>                 URL: https://issues.apache.org/jira/browse/HIVE-7113
>             Project: Hive
>          Issue Type: New Feature
>          Components: Query Processor
>            Reporter: Navis
>            Assignee: Navis
>            Priority: Minor
>         Attachments: HIVE-7113.1.patch.txt
>
>
> Mostly, partitioned table has the same storage description with mother table just except data location. If partitions can be forced not to have different schema with table by configuration, the time for retrieving partition objects from metastore and for creating serde for each partition could be nullified.



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