Member since
05-05-2017
4
Posts
0
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
3656 | 05-18-2018 07:33 PM |
05-18-2018
07:33 PM
I was able to resolve this by modifying the Azure Blob Properties. To navigate to the Blob Properties:
Containers > [container] > [blob] In the Metadata section of Blob Properties, modify the key hdi_permission "owner" value to the user executing the Hive process. For this proof of concept, user "Hive" is executing the Hive CREATE TABLE so I changed the original value from... {"owner":"root","group":"supergroup","permissions":"rw-r--r--"} to... {"owner":"hive","group":"supergroup","permissions":"rw-r--r--"} The hdi_permission value must be changed for each blob. Since WASB is flat storage, which only emulates a folder hierarchy, that means that each file will need to have the value changed.
... View more