|
@@ -811,42 +811,33 @@ The region should be set to the AWS region corresponding to the S3 account. By d
|
|
|
**Using Ceph**
|
|
**Using Ceph**
|
|
|
New end points have been added in [HUE-5420](https://issues.cloudera.org/browse/HUE-5420)
|
|
New end points have been added in [HUE-5420](https://issues.cloudera.org/browse/HUE-5420)
|
|
|
|
|
|
|
|
|
|
+### Azure File Systems
|
|
|
|
|
|
|
|
-### ADLS / ABFS
|
|
|
|
|
|
|
+Hue's file browser can now allow users to explore, manage, and upload data in an ADLS v1 or ADLS v2 (ABFS), in addition to HDFS and S3.
|
|
|
|
|
|
|
|
-Hue's file browser can now allow users to explore, manage, and upload data in an ADLS v1 or ADLS v2 (ABFS), in addition to HDFS and S3. ABFS is currently a work in progress with [HUE-8908](https://issues.cloudera.org/browse/HUE-8908)
|
|
|
|
|
|
|
+Read more about it in the [ADLS User Documentation](/user/browsing#adls-abfs).
|
|
|
|
|
|
|
|
-Read more about it in the [ADLS User Documentation](/user/browsing#adls).
|
|
|
|
|
-
|
|
|
|
|
-In order to add an ADLS account to Hue, you'll need to configure Hue with valid ADLS credentials, including the client ID, client secret and tenant ID.
|
|
|
|
|
|
|
+In order to add an Azure account to Hue, you'll need to configure Hue with valid Azure credentials, including the client ID, client secret and tenant ID.
|
|
|
These keys can securely stored in a script that outputs the actual access key and secret key to stdout to be read by Hue (this is similar to how Hue reads password scripts). In order to use script files, add the following section to your hue.ini configuration file:
|
|
These keys can securely stored in a script that outputs the actual access key and secret key to stdout to be read by Hue (this is similar to how Hue reads password scripts). In order to use script files, add the following section to your hue.ini configuration file:
|
|
|
|
|
|
|
|
- [adls]
|
|
|
|
|
|
|
+ [azure]
|
|
|
[[azure_accounts]]
|
|
[[azure_accounts]]
|
|
|
[[[default]]]
|
|
[[[default]]]
|
|
|
client_id_script=/path/to/client_id_script.sh
|
|
client_id_script=/path/to/client_id_script.sh
|
|
|
client_secret_script=/path/to/client_secret_script.sh
|
|
client_secret_script=/path/to/client_secret_script.sh
|
|
|
tenant_id_script=/path/to/tenant_id_script.sh
|
|
tenant_id_script=/path/to/tenant_id_script.sh
|
|
|
|
|
|
|
|
- [[adls_clusters]]
|
|
|
|
|
- [[[default]]]
|
|
|
|
|
- fs_defaultfs=adl://<account_name>.azuredatalakestore.net
|
|
|
|
|
- webhdfs_url=https://<account_name>.azuredatalakestore.net
|
|
|
|
|
-
|
|
|
|
|
- [[abfs_clusters]]
|
|
|
|
|
- [[[default]]]
|
|
|
|
|
- fs_defaultfs=abfss://<container_name>@<account_name>.dfs.core.windows.net
|
|
|
|
|
- webhdfs_url=https://<container_name>@<account_name>.dfs.core.windows.net
|
|
|
|
|
-
|
|
|
|
|
Alternatively (but not recommended for production or secure environments), you can set the client_secret value in plain-text:
|
|
Alternatively (but not recommended for production or secure environments), you can set the client_secret value in plain-text:
|
|
|
|
|
|
|
|
- [adls]
|
|
|
|
|
|
|
+ [azure]
|
|
|
[[azure_account]]
|
|
[[azure_account]]
|
|
|
[[[default]]]
|
|
[[[default]]]
|
|
|
client_id=adlsclientid
|
|
client_id=adlsclientid
|
|
|
client_secret=adlsclientsecret
|
|
client_secret=adlsclientsecret
|
|
|
tenant_id=adlstenantid
|
|
tenant_id=adlstenantid
|
|
|
|
|
|
|
|
|
|
+The account name used by ADLS / ABFS will need to be configured via the following properties:
|
|
|
|
|
+
|
|
|
[[adls_clusters]]
|
|
[[adls_clusters]]
|
|
|
[[[default]]]
|
|
[[[default]]]
|
|
|
fs_defaultfs=adl://<account_name>.azuredatalakestore.net
|
|
fs_defaultfs=adl://<account_name>.azuredatalakestore.net
|