Publishing Dialog

When a job has successfully completed, you can publish your job results to one of your connected datastores. In the Job Details page, click the Output Destinations tab. Then, click Publish.

Publish to Cloudera Navigator

If you have enabled the Designer Cloud Powered by Trifacta® platform to integrate with Cloudera Navigator, metadata information is automatically published to Cloudera Navigator.

Locating your job metadata in Cloudera Navigator:

1. In the Job Details page, acquire the job ID from the Job summary in the Overview tab.
2. Login to Navigator.
3. Search for trifacta.<jobId>.

4. If the job completed successfully and Navigator has been able to poll the platform for new job results, you should see individual entries for each sub-job of the job that completed:
   
   

   sub-job identifier	Description
   trifacta.<jobId>.wrangle.<subJobId1>	Link to metadata on transformation job that was executed on the running environment.
   trifacta.<jobId>.filewriter.<subJobId2>	Link to metadata on job that generated the results in the targeted datastore.

5. Click any of these links to review metadata details about the job.

Publish to Hive

If you have enabled publishing to Hive, you can specify the database and table to which you would like to publish results.

Administrators can connect the Designer Cloud Powered by Trifacta platform to an available instance of Hive. For more information, see Configure for Hive.

Hive publishing options:

• Database: Name of Hive database. This value is case-insensitive.

  NOTE: You cannot publish to a Hive database that is empty. The database must contain at least one table.

• Table: Name of Hive table in database. A default value is generated based on your dataset name. This value is case-insensitive.
• Format: Choose publishing format: avro or pqt (parquet).

Data Option:

If you are publishing to a pre-existing table, schema validation is automatically performed.

• Create new table & load data: The platform creates the table and then loads it with the results from this job. If you attempt to use this option on a table that already exists, the publishing job fails, and an error is generated in the log.

• Append data to existing table: The results from this job are appended to the data that is already stored in the table, which already exists in the Hive database. If you attempt to append to a table that does not exist, the publishing job fails, and an error is generated in the log.

  Tip: Optionally, users can be permitted to publish to Hive staging schemas to which they do not have full create and drop permissions. This feature must be enabled. For more information, see Configure for Hive.

  When enabled, the name of the staging DB must be inserted into your user profile. See User Profile Page.

• Truncate table & load data: Data is cleared from the target table, and new data is added to the existing schema.
• Drop, recreate table & load data: Target table is dropped. A new table is created using the schema of the generated output and filled with the job results.

To export the job results to the designated Hive table, click Publish. Publication happens in the background as a Alteryx job. You can track status in the Jobs page. See Jobs Page.

Publish to SQL DW

To publish to Microsoft SQL DW storage, please specify the following information.

Options:

• Database: Name of SQL DW database. This value is case-insensitive.

  NOTE: You cannot publish to a SQL DW database that is empty. The database must contain at least one table.

• Schema: Name of the schema to use to publish. Schema and results must match in terms of column names, order, and data type.
• Table: Name of table in database. A default value is generated based on your dataset name. This value is case-insensitive.

Data Option:

If you are publishing to a pre-existing table, schema validation is automatically performed.

• Create new table & load data: The platform creates the table and then loads it with the results from this job. If you attempt to use this option on a table that already exists, the publishing job fails, and an error is generated in the log.
• Append data to existing table: The results from this job are appended to the data that is already stored in the table, which already exists in the Hive database. If you attempt to append to a table that does not exist, the publishing job fails, and an error is generated in the log.
• Truncate table & load data: Data is cleared from the target table, and new data is added to the existing schema.
• Drop, recreate table & load data: Target table is dropped. A new table is created using the schema of the generated output and filled with the job results.

Publish to Redshift

If you have enabled publishing to Redshift, you can specify the database, schema, and table to which you would like to publish results.

Notes:

• When launching the job, your output must be delivered to S3 with results in Avro, CSV, or JSON format.

  A Redshift connection requires S3 as your base storage layer. See Set Base Storage Layer.
• When publishing output results to Redshift, you cannot publish CSV files with headers. You can publish single-file CSV without headers and multi-file CSV outputs, which have no headers by default.

Administrators can connect the Designer Cloud Powered by Trifacta platform to an available instance of Redshift. For more information, see Create Redshift Connections.

Publish to Tableau

If you have created a Tableau Server connection, you can export results that have been generated in TDE format to the connected server.

Options:

• Connection: If you have created multiple connections to Tableau Server, please select the connection to use from the list.
  • The Site name is specified as part of the connection. See Create Tableau Server Connections.
• Project Name: Name of the Tableau Server project.
• Datasource Name: Name of the Tableau Server datasource. This value is displayed for selection in Tableau Server.

Data Option:

If you are publishing to a pre-existing table, schema validation is automatically performed.

• Create new datasource: The platform creates the datasource and then loads it with the results from this job. If you attempt to use this option on a source that already exists, the publishing job fails, and an error is generated in the log.
• Append data to existing datasource: The results from this job are appended to the data that is already stored in Tableau Server. If you attempt to append to a source that does not exist, the publishing job fails, and an error is generated in the log. Append operations also fail if you publish to a target with a different schema.
• Replace contents of existing datasource: Target datasource is dropped. A new datasource is created using the schema of the generated output and filled with the job results.