Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Bolo.

Table of Contents

Search

  1. Introducing Mass Ingestion
  2. Getting Started with Mass Ingestion
  3. Connectors and Connections
  4. Mass Ingestion Applications
  5. Mass Ingestion Databases
  6. Mass Ingestion Files
  7. Mass Ingestion Streaming
  8. Monitoring Mass Ingestion Jobs
  9. Asset Management
  10. Troubleshooting

Mass Ingestion

Mass Ingestion

Overriding schema drift options when resuming a database ingestion job

Overriding schema drift options when resuming a database ingestion job

You can override the schema drift options when you resume a
database ingestion
job that is in the Stopped, Aborted, or Failed state. The overrides affect only those tables that are currently in the Error state because of the
Stop Table
or
Stop Job
Schema Drift option. Use the overrides to correct or resolve these errors.
You can override schema drift options and resume an incremental load job or a combined initial and incremental load job either from the
My Jobs
page in the
Mass Ingestion
service or from the
All Jobs
tab on the
Mass Ingestion
page in
Operational Insights
or
Monitor
.
  1. Navigate to the row for the job that you want to resume with an override.
  2. In the Actions menu for the row, click
    Resume With Options
    .
    The
    Resume With Options
    command is not available if the job is in the
    Failed
    state because the task deployment failed.
    The
    Resume Options
    dialog box appears.
  3. In the
    Schema Drift Options
    list, select the schema drift option that will be used to process the DDL operation on the source that caused the database ingestion job to stop.
    The following table describes the schema drift options:
    Option
    Description
    Ignore
    Do not replicate DDL changes that occur on the source database to the target.
    Stop Table
    Stop processing the source table on which the DDL change occurred.
    The database ingestion job cannot retrieve the data changes that occurred on the source table after the job stopped processing it. Consequently, data loss might occur on the target. To avoid data loss, you will need to resynchronize the source and target objects that the job stopped processing. Use the
    Resume With Options
    Resync
    option.
    Resync
    Resynchronize the target table with the source table. Use this option for tables that the job stopped processing because of the
    Stop Table
    setting for a
    Schema Drift
    option.
    This option is available only for combined initial and incremental load jobs.
    Replicate
    Allow the database ingestion job to replicate the DDL change to the target.
    If you specify the
    Replicate
    option for Rename Column operations on Microsoft Azure Synapse Analytics targets, the job will end with an error.
  4. Click
    Resume With Options
    .
    The resumed job will use the schema drift option that you specified in step 3 to process the schema change that caused the job to stop. Thereafter, the schema drift options that you specified when creating the task take effect again.
    Mass Ingestion Databases
    processes a schema change to a source table only after a DML operation occurs on the table. Therefore, after you resume a job, the table subtask state remains unchanged until the first DML operation occurs on the table.

0 COMMENTS

We’d like to hear from you!