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

Aborting a database ingestion job

Aborting a
database ingestion
job

You can abort a
database ingestion
job that is in the
Up and Running
,
Running with Warning
,
On Hold
, or
Stopping
state.
For an incremental load job, the job stops immediately after a checkpoint is taken. A checkpoint records the point in the change stream where incremental processing left off for recovery purposes.
For a combined initial and incremental load job, any
running
initial load subtasks stop immediately. For the incremental load portion of the job, a checkpoint is taken and then the job stops.
For an initial load job, any
running
subtasks stop immediately and then the job stops. Non-running subtasks remain in their current states.
  1. From the Actions menu for the job, select
    Abort
    .
    The job state switches to
    Aborting
    and then to
    Aborted
    .
    For initial load jobs, the state of started and running subtasks switches to
    Aborted
    . For incremental load or combined initial and incremental load jobs, the state of subtasks switches to
    Stopped
    .

0 COMMENTS

We’d like to hear from you!