If you have integrated the with Hive, you can integrate it with Alation to simplify finding datasets within Hive for import. The Alation integration supports the following methods:
Alation is a data catalog service for Hive. For more information, see www.alation.com.
Alation version 4.10.0 or later
Your enterprise environment must have a deployed instance of Hive to which the has already been integrated. See Configure for Hive.
You must have credentials to access Alation. You can sign up through the Alation Catalog Navigator after the integration is complete.
NOTE: Your Hive administrator and Alation administrator must ensure that your accounts have the appropriate permissions to search for and access datasets within these separate deployments. |
Steps:
NOTE: Although the integration to Alation appears as a connection in the application, the connection cannot be created through the application. Please complete the following steps. |
alation
.
Property | Description | |
---|---|---|
| This value identifies the path on the Alation server to where their integration SDK is stored. Do not modify this value. | |
| Set this value true to enable the integration. | |
| Set this value to the URL of the web interface for the Alation deployment. |
Try running a simple job. For more information, see Verify Operations.
If ad-hoc publishing to Hive has been enabled, you can export the generated results to Hive and then attempt to re-import through Alation.
NOTE: There may be a delay before the |
Optionally, you can enable Alation users to open Hive tables from Alation in the .
NOTE: To support this integration, end users must disable popup blockers in the browser. For more information, please see your browser's documentation. |
NOTE: If Kerberos is enabled, you must be authenticated into the |
NOTE: HTTPS is not supported. |
Steps:
Visit the following URL:
http://<alation_host>/admin/misc |
Paste the API token into the following cURL command and execute it.
HTTP:
curl -X POST 'http://<alation_host>/integration/catalog_chooser/register_opener/' -H "Content-Type: application/json" -H "Token: <token_key>" -d '{"endpoint":"http://<platform_host>:<platform_port_num>/import/data?uri=${dataSource.jdbcUri}&table=${qualifiedName}","endpoint_type":"NAVIGATE","name":"Trifacta","accept_object_types":["table"],"accept_data_source_types":["hive", "hive2"]}' |
HTTPS: Change the protocol identifier for both URLs to https
and remove the platform port number.
curl -X POST 'https://<alation_host>/integration/catalog_chooser/register_opener/' -H "Content-Type: application/json" -H "Token: <token_key>" -d '{"endpoint":"https://<platform_host>/import/data?uri=${dataSource.jdbcUri}&table=${qualifiedName}","endpoint_type":"NAVIGATE","name":"Trifacta","accept_object_types":["table"],"accept_data_source_types":["hive", "hive2"]}' |
where:
Parameter | Description |
---|---|
<alation_host> | Hostname of the Alation server |
<token_key> | The token value that was generated in Alation |
<platform_host> | Hostname of the |
<platform_port_num> | Port number of the |
A successful execution of the above command logs the following JSON message:
{"id":1,"name":"Trifacta","endpoint":"http://<platform_host>:<platform_port_num>/import/data","accept_object_types":["table"],"accept_data_source_types":["hive", "hive2"]} |
Steps:
For more information, see Import Data Page.