Metadata import jobs

A metadata import job is created automatically when you create a metadata import asset.

The default job name is metadata-import-name job but you can choose a different name when you create the metadata import asset. However, you can't change the name later.

To view details about a metadata import job, you can use one of these methods:

  • On the project's Jobs page, find the job and click it.
  • Within the metadata import asset, click the link to the job that is available in the asset details.

From the job's details page, you can view its runs and the status of each run. For details about pausing and resuming jobs, see Pausing and resuming jobs.

Starting
The job is initialized.
Running
Processing is in progress.
Pausing
Processing is being paused. It might take a while.
Paused
Processing is temporarily stopped.
Resuming
After the process was paused, it is starting to run again. It might take a while.
Canceled
A user canceled the job run.
Completed
All assets were successfully imported.
Completed with warnings
Processing completed but some assets had to be skipped, for example, because they did not exist in the data source.
Completed with errors
Processing completed but some assets could not be imported, for example, due to a timeout.
Failed
Processing stopped unexpectedly.

If a run completed with warnings or errors, or failed altogether, you can select the run and view the log tail or download the entire log file to help you troubleshoot the run.

Pausing and resuming jobs

When you import lineage metadata, you can pause a running job and resume it later. This option is useful for large imports that can run for several days. For example, you can pause a job during business hours and resume it later to avoid affecting daily operations.

You can pause and resume lineage import jobs and asset import jobs for which you use data lineage connectors. If you run a combined import of assets and lineage, you cannot pause or resume the job.

The behavior of a paused job depends on the phase that is running when you pause it.

Pausing in the middle of the phase
The job is paused immediately, even if the phase is still in progress. When you resume the job, it continues from the point where it stopped. This behavior applies in the following cases:

  • When you pause the job during the analysis phase for data sources with input-level processing:
    • Apache Hive
    • Db2
    • Db2 for z/OS
    • Db2 on Cloud
    • Microsoft Azure SQL Database
    • Microsoft Power BI (Azure)
    • Microsoft SQL Server
    • Oracle
    • Snowflake
    • Statistical Analysis System (SAS)
    • Talend

Pausing after the phase is completed
The job is paused only after the current phase finishes. The status Pausing might be displayed for some time, depending on how much data remains to be processed. When you resume the job, it starts with the next phase. This behavior applies in all other cases.

Learn more