In the Run Job page, you can specify transformation and profiling jobs for the currently loaded dataset. Available options include output formats and output destinations.
You can also configure the environment where the job is to be executed.
Tip: Columns that have been hidden in the Transformer page still appear in the generated output. Before you run a job, you should verify that all currently hidden columns are ok to include in the output.
Run Job Page
Select the environment where you wish to execute the job. Some of the following environments may not be available to you. These options appear only if there are multiple accessible running environments.
NOTE: Running a job executes the transformations on the entire dataset and saves the transformed data to the specified location. Depending on the size of the dataset and available processing resources, this process can take a while.
Tip: The application attempts to identify the best running environment for you. You should choose the default option, which factors in the available environments and the size of your dataset to identify the most efficient processing environment.
: Executes the job on the running environment hosted on the same server as the .
Hadoop: Executes the job using the configured running environment for your Hadoop cluster.
Profile Results: Optionally, you can disable profiling of your output, which can improve the speed of overall job execution. When the profiling job finishes, details are available through the Job Results page, including links to download results.
NOTE: Percentages for valid, missing, or mismatched column values may not add up to 100% due to rounding.This issue applies to the Photon running environment.
See Job Results Page.
You can add, remove, or edit the outputs generated from this job. By default, a CSV output for your home directory on the selected datastore is included in the list of destinations, which can be removed if needed. You must include at least one output destination.
From the available datastores in the left column, select the target for your publication.
Add Publishing Action
NOTE: Do not create separate publishing actions that apply to the same file or database table.
New/Edit: You can create new or modify existing connections. See Create Connection Window.
If Hive publishing is enabled, you must select or specify a database table to which to publish.
Depending on the running environment, results are generated in Avro or Parquet format. See below for details on specifying the action and the target table.
If you are publishing a wide dataset to Hive, you should generate results using Parquet.
For more information on how data is written to Hive, see Hive Data Type Conversions.
Locate a publishing destination: Do one of the following.
NOTE: The publishing location must already exist before you can publish to it. The publishing user must have write permissions to the location.
NOTE: If your HDFS environment is encrypted, the default output home directory for your user and the output directory where you choose to generate results must be in the same encryption zone. Otherwise, writing the job results fails with a
Choose an existing file or folder: When the location is found, select the file to overwrite or the folder into which to write the results.
NOTE: You must have write permissions to the folder or file that you select.
Create a new file: See below.
To save the publishing destination, click Save Settings.
If the underlying datasets use variable parameters, you can apply overrides to the default values of the variables. Click the listed default value and insert a new value.
NOTE: Variable overrides apply only to this job. Subsequent jobs use the default variable values, unless specified again. No data validation is performed on entries for override values.
For more information on variables, see Overview of Parameterization.
When you generate file-based results, you can configure the filename, storage format, compression, number of files, and the updating actions in the right-hand panel.
Output File Settings
Configure the following settings.
To change it, navigate to the proper directory.
Avro:This format is used to support data serialization within a Hadoop environment.
CSV and JSON: These formats are supported for all types of imported datasets and all running environments.
Publishing action: Select one of the following:
myOutput_3.csv, and so on).
Append to this file every run: For each job run with the selected publishing destination, the same file is appended, which means that the file grows until it is purged or trimmed.
NOTE: When publishing single files to S3, the
NOTE: When appending data into a Hive table, the columns displayed in the Transformer page must match the order and data type of the columns in the Hive table.
NOTE: This file is not available for outputs in TDE format.
NOTE: Compression of published files is not supported for an
Include headers as first row: For CSV outputs, you can choose to include the column headers as the first row in the output. For other formats, these headers are included automatically.
NOTE: Headers cannot be applied to compressed outputs.
Single File: Output is written to a single file.
When publishing to Hive, please complete the following steps to configure the table and settings to apply to the publish action.
NOTE: Some may be exported to Hive using different data types. For more information on how types are exported to Hive, see Hive Data Type Conversions.
Output database: To change the database to which you are publishing, click the Hive icon in the sidebar. Select a different database.
NOTE: You cannot publish to a Hive database that is empty. The database must contain at least one table.
If you are creating a publishing action for a Redshift database table, you must provide the following information.
NOTE: Some may be exported to Redshift using different data types. For more information, see Redshift Data Type Conversions.
Output database: To change the database to which you are publishing, click the Redshift icon in the sidebar. Select a different database.
To execute the job as configured, click Run Job. The job is queued for execution.
After a job has been queued, you can track its progress toward completion. See Dataset Details Page.
You can use the available REST APIs to execute jobs for known datasets. For more information, see API JobGroups Create v3.
For more information on the entire API workflow, see API Workflow - Develop a Flow.
provides a command line interface that enables administrators to execute and monitor from the command line. As needed, completed jobs can be published to other datastores.
For more information, see CLI for Jobs.