Mass Ingestion

Back Next

Configuring schedule and runtime options

On the

Schedule and Runtime Options

page in the

application ingestion

task wizard, you can specify a schedule for running the initial load jobs and configure the runtime options for jobs of all load types.

In the

Schema Drift Options

section, specify the schema drift option to use for each type of Data Definition Language (DDL) operation.

The

Schema Drift Options

section appears only for incremental load and combined initial and incremental load tasks.

Mass Ingestion Applications

supports the following types of DDL operations:

Add Field

Modify Field

Drop Field

Rename Field

The following table describes the schema drift options that you can specify for the DDL operations:

Option	Description
Ignore	Does not replicate DDL changes that occur on the source schema to the target. For Amazon Redshift, Microsoft Azure Synapse Analytics, and Snowflake targets, this option is the default option for the Drop Field and Rename Field operation types. For Google BigQuery targets, this option is the default option for all the operation types.
Replicate	Allows the application ingestion job to replicate the DDL changes to the target. For Amazon Redshift, Microsoft Azure Synapse Analytics, and Snowflake targets, this option is the default option for the Add Field and Modify Field operation types. For Amazon S3, Google Cloud Storage, and Microsoft Azure Data Lake Storage Gen2, targets, this option is the default option for all types of DDL operations. For Google Big Query targets, this option is the default option for Add Field and Drop Field operation types. If you try to replicate an unsupported schema change type on the target, the application ingestion jobs associated with the task will fail with an error. Add Field operations that add a primary-key field are not supported and might cause unpredictable results. Modify Field operations that change the NULL or NOT NULL constraint of a field are not replicated to the target.
Stop Job	Stops the application ingestion job.
Stop Object	Stops processing the source object on which the DDL change occurred. When one or more objects are excluded from replication because of the Stop Object schema drift option, the status of the job changes to Running with Warning . The application ingestion job cannot retrieve the data changes that occurred on the source object after the job stops processing the changes. This action leads to data loss on the target. To avoid data loss, you must re-synchronize the source and target objects that the job stopped processing before you resume the application ingestion job.

Optionally, in the

Advanced

section, modify the value in the

Number of Rows in Output File

value to specify the maximum number of rows that the

application ingestion

task writes to an output file on the target.

Valid values are 1 through 100000000 and the default value is 100000 rows.

For incremental load and combined initial and incremental load operations, change data is flushed to the target either when the specified number of rows is reached or when the flush latency period expires and the job is not in the middle of processing a transaction. The flush latency period is the time that the job waits for more change data before flushing data to the target. The latency period is set to 10 seconds and cannot be changed.

If you want the

application ingestion

job associated with the task to run in specific intervals based on a schedule, select

Run this task based on a schedule

in the

Schedule

section, and then select a predefined schedule for the job.

By default,

Do not run this task based on a schedule

is selected, which configures the job to run only when it is manually triggered.

This field is available only for initial load tasks.

You can view and edit the job schedule options in Administrator. If you edit the schedule, the changes are automatically applied to all the jobs that are configured to run based on the schedule. If you change the schedule for a task that is already deployed, the updated schedule is automatically applied to the

application ingestion

job associated with the task.

If a job is about to be triggered based on its schedule when its previous run is still in progress,

Mass Ingestion Applications

does not run the job and allows the job run that is already in progress to complete.

In the

Custom Properties

section, you can specify custom properties that Informatica provides for special cases. To add a property, click the

Add Property

icon, and then add the property name and value.

The custom properties are configured to address unique environments and special use cases.

Specify the custom properties only at the direction of Informatica Global Customer Support.

Rename Saved Search

Table of Contents

Mass Ingestion

Mass Ingestion

Configuring schedule and runtime options

Configuring schedule and runtime options