[
https://issues.apache.org/jira/browse/HIVE-27970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800995#comment-17800995
]
Butao Zhang commented on HIVE-27970:
------------------------------------
I think this related to the ticket
https://issues.apache.org/jira/browse/HIVE-1707, before HIVE-1707, you can
insert data to its correct partition's schema path instead of its table's
schema.
[https://community.cloudera.com/t5/Community-Articles/Hive-partitions-on-different-Namespaces-in-a-Federated/ta-p/248041]
here is a blog about how to store partiton data into different
schema(hdfs://ns1, hdfs://ns2). Note this blog can not fix your issue at
bottom, it's just a workaround. Just fyi.
But I think your use case is reasonable, especially in large hdfs cluster. We
need to optimize this issue at its root.
> Single Hive table partitioning to multiple storage system- (e.g, S3 and HDFS)
> -----------------------------------------------------------------------------
>
> Key: HIVE-27970
> URL: https://issues.apache.org/jira/browse/HIVE-27970
> Project: Hive
> Issue Type: Improvement
> Affects Versions: 3.1.2
> Reporter: zhixingheyi-tian
> Priority: Major
>
> Single Hive/Datasource table partitioning to multiple storage system- (e.g,
> S3 and HDFS)
> For Hive table:
>
> {code:java}
> CREATE TABLE htable a string, b string) PARTITIONED BY ( p string )
> location "hdfs://{cluster}}/user/hadoop/htable/";
> alter table htable add partition(p='p1') location
> 's3a://{bucketname}/usr/hive/warehouse/htable/p=p1';
> {code}
>
> When inserting into htable, or insert overwrite htable. New data of “p=p1”
> will insert table location storage. This does not meet the requirements.
> Is there any best practise? Or is there a plan to support this feature?
> Thanks!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
