Review

The Review step lets you review details of your DQ job, including Job Name, Run Date, and the SQL query. You can also edit the run command from the Command Line option when using Pullup mode. Select from one of the options below depending on whether you are using Pullup or Pushdown mode.

Pullup
Pushdown

Pullup job review screenshot

No.	Option	Description
	Job Name	The name of your DQ job. Job names must be unique per data source connection. For example, two jobs created on a PostgreSQL connection cannot both be named example.job. To avoid an error when you attempt to run the job in this scenario, you can name the second job example.job_2 to distinguish between the two. Click the to update the name. Click the to save your changes.
	Run Date	The datetime that is substituted in your timeslice filter. Click the to update the name. Click the and select a date, then click and drag the dial to select a time. Click the to save your changes.
	Query, Command Line, and JSON tabs	Query is the SQL query that automatically compiles according to your selections in the Select Columns, Select Rows, and Add Layers activities. Note This is a read-only option. To make changes to the SQL query, return to a previous step and update your selections accordingly. Command Line is the Spark SQL run command of your DQ job, where the various inputs from the settings you selected in the previous steps are reflected in the query. Spaces in column names are not supported when editing the command line. JSON is the JSON payload that reflects the settings you specified in the previous steps. You can manually edit this and copy the output to your notebook.

No.

Option

Description

Job Name

The name of your DQ job.

Job names must be unique per data source connection. For example, two jobs created on a PostgreSQL connection cannot both be named example.job. To avoid an error when you attempt to run the job in this scenario, you can name the second job example.job_2 to distinguish between the two.

Click the to update the name. Click the to save your changes.

Run Date

The datetime that is substituted in your timeslice filter.

Click the to update the name. Click the and select a date, then click and drag the dial to select a time. Click the to save your changes.

Query, Command Line, and JSON tabs

Query is the SQL query that automatically compiles according to your selections in the Select Columns, Select Rows, and Add Layers activities.

Note This is a read-only option. To make changes to the SQL query, return to a previous step and update your selections accordingly.

Command Line is the Spark SQL run command of your DQ job, where the various inputs from the settings you selected in the previous steps are reflected in the query. Spaces in column names are not supported when editing the command line.

JSON is the JSON payload that reflects the settings you specified in the previous steps. You can manually edit this and copy the output to your notebook.

DQ Pushdown job review screenshot

No.	Option	Description
	Job Name	The name of your DQ job. Job names must be unique per data source connection. For example, two jobs created on a Snowflake connection cannot both be named example.job. To avoid an error when you attempt to run the job in this scenario, you can name the second job example.job_2 to distinguish between the two. Click the to update the name. Click the to save your changes.
	Run Date	The datetime that is substituted in your timeslice filter. Click the to update the name. Click the and select a date, then click and drag the dial to select a time. Click the to save your changes.
	Query	The SQL query that automatically compiles according to your selections in the Select Columns, Select Rows, and Add Layers activities. Note This is a read-only option. To make changes to the SQL query, return to a previous step and update your selections accordingly.

No.