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.
NOTE: You cannot publish ad-hoc results for a job when another publishing job is in progress for the same job through the application or the command line interface. Please wait until the previous job has been published before retrying to publish the failing job. This is a known issue. |
NOTE: If you run a job and then attempt to export the results to a relational source, Datetime columns are written in the relational table as String values. Direct publication of Datetime columns publishes the output in the designated target data type. For more information, see Type Conversions. |
NOTE: If you run a job with a single relational target and it fails at the publication step, you cannot publish the transformation job through the Export Results window. |
NOTE: JSON-formatted files that are generated by |
Export Results window |
NOTE: If you created a publishing action to deliver results to Hive as part of this job definition, the Hive tab identifies the database and table where the results were written. Any available options are for ad-hoc publishing of results to Hive. |
If you have enabled publishing to Hive, you can specify the database and table to which you would like to publish results.
NOTE: When launching the job, you must choose to generate results in Avro or Parquet format to publish to Hive. If you are publishing a wide dataset to Hive, you should generate results using Parquet. |
NOTE: Some |
Administrators can connect the 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. |
Data Option:
If you are publishing to a pre-existing table, schema validation is automatically performed.
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. |
To export the job results to the designated Hive table, click Publish. Publication happens in the background as a . You can track status in the Jobs page. See Jobs Page.
To publish to Microsoft SQL DW storage, please specify the following information.
NOTE: Publishing to Microsoft SQL DW requires deployment of the |
NOTE: Results must be in Parquet format to publish to SQL DW. |
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. |
Data Option:
If you are publishing to a pre-existing table, schema validation is automatically performed.
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.Administrators can connect the to an available instance of Redshift. For more information, see Create Redshift Connections.
If you have created a Tableau Server connection, you can export results that have been generated in TDE format to the connected server.
NOTE: Generated results must be in TDE format for export. |
NOTE: If you encounter errors generating results in TDE format, additional configuration may be required. See Supported File Formats. |
Options:
Data Option:
If you are publishing to a pre-existing table, schema validation is automatically performed.