[
https://issues.apache.org/jira/browse/HIVE-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840934#action_12840934
]
Raghotham Murthy commented on HIVE-1002:
----------------------------------------
i think its probably ok to specify which columns to partition on. We should not
have implied ordering/hierarchy of keys. It might be better if the user
specifies the order.
Something like,
{code}
insert overwrite T partitioned on (col[=value], (col[=value])*)
{code}
Then users can specify constant values or if no value is present, use the
column value in the data. In addition, this will allow users to specify the
order of partitioning as well.
> multi-partition inserts
> -----------------------
>
> Key: HIVE-1002
> URL: https://issues.apache.org/jira/browse/HIVE-1002
> Project: Hadoop Hive
> Issue Type: New Feature
> Reporter: Zheng Shao
> Assignee: Ning Zhang
>
> We should allow queries like this into a partitioned table:
> {code}
> CREATE TABLE (a STRING, b STRING, c STRING)
> PARTITIONED BY (ds STRING, ts STRING);
> INSERT OVERWRITE TABLE x PARTITION (ds = '2009-12-12')
> SELECT a, b, c, ts FROM xxx;
> {code}
> Basically, allowing users to overwrite multiple partitions at a time.
> The partition values specified in PARTITION part (if any) should be a prefix
> of the partition keys.
> The rest of the partition keys goes to the end of the SELECT expression list.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
