[
https://issues.apache.org/jira/browse/HIVE-23388?focusedWorklogId=455549&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-455549
]
ASF GitHub Bot logged work on HIVE-23388:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 07/Jul/20 15:27
Start Date: 07/Jul/20 15:27
Worklog Time Spent: 10m
Work Description: nrg4878 commented on pull request #1117:
URL: https://github.com/apache/hive/pull/1117#issuecomment-654941642
Fix has been merged.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 455549)
Time Spent: 0.5h (was: 20m)
> CTAS queries should use target's location for staging.
> ------------------------------------------------------
>
> Key: HIVE-23388
> URL: https://issues.apache.org/jira/browse/HIVE-23388
> Project: Hive
> Issue Type: Sub-task
> Components: HiveServer2
> Affects Versions: 4.0.0
> Reporter: Naveen Gangam
> Assignee: Naveen Gangam
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In cloud based storage systems, renaming files across different root level
> buckets seem to be disallowed. The S3AFileSystem throws the following
> exception. This appears to be bug in S3FS impl.
> Failed with exception Wrong FS
> s3a://hive-managed/clusters/env-xxxxx/warehouse-xxxx-xxxx/warehouse/tablespace/managed/hive/tpch.db/customer/delta_0000001_0000001_0000
> -expected s3a://hive-external
> 2020-04-27T19:34:27,573 INFO [Thread-6] jdbc.TestDriver:
> java.lang.IllegalArgumentException: Wrong FS
> s3a://hive-managed//clusters/env-xxxx/warehouse-xxxx-xxxx/warehouse/tablespace/managed/hive/tpch.db/customer/delta_0000001_0000001_0000
> -expected s3a://hive-external
> But we should fix our query plans to use the target table's directory for
> staging as well. That should resolve this issue and it is the right thing to
> do as well (in case there are different encryption zones/keys for these
> buckets).
> Fix in HIVE-22995 probably changed this behavior.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
