You can run the following kinds of metadata import jobs:
Full sync of entries with incremental import of their aspects.
Supported for custom entries.
Incremental import of aspects only. Supported for aspects that
belong to custom entries and system entries. For custom entries,
you can modify both optional aspects and required aspects. For
system entries, you can modify optional aspects.
Attributes
Name
Description
source_storage_uri
str
Optional. The URI of a Cloud Storage bucket or folder
(beginning with gs:// and ending with /) that
contains the metadata import files for this job.
A metadata import file defines the values to set for each of
the entries and aspects in a metadata import job. For more
information about how to create a metadata import file and
the file requirements, see `Metadata import
file
source_create_time
google.protobuf.timestamp_pb2.Timestamp
Optional. The time when the process that
created the metadata import files began.
google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec.LogLevel
Optional. The level of logs to write to Cloud Logging for
this job.
Debug-level logs provide highly-detailed information for
troubleshooting, but their increased verbosity could incur
`additional
costs
A boundary on the scope of impact that the metadata import
job can have.
LogLevel
LogLevel(value)
The level of logs to write to Cloud Logging for this job.
Depending on the size of your metadata job and the number of
logs that are generated, debug-level logging might incur
`additional
costs <https://cloud.google.com/stackdriver/pricing>`__.
INFO (2):
Info-level logging. Captures logs at the
overall job level. Includes aggregate logs about
import items, but doesn't specify which import
item has an error.
SyncMode
SyncMode(value)
Specifies how the entries and aspects in a metadata import job are
updated. For more information, see Sync
mode <https://cloud.google.com/dataplex/docs/import-metadata#sync-mode>__.
This sync mode is supported for entries.
INCREMENTAL (2):
Only the resources that are explicitly
included in the metadata import file are
modified. Use this mode to modify a subset of
resources while leaving unreferenced resources
unchanged.
This sync mode is supported for aspects.
NONE (3):
If entry sync mode is `NONE`, then aspects are modified
according to the aspect sync mode. Other metadata that
belongs to entries in the job's scope isn't modified.
This sync mode is supported for entries.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Class ImportJobSpec (2.11.0)\n\nVersion latestkeyboard_arrow_down\n\n- [2.11.0 (latest)](/python/docs/reference/dataplex/latest/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [2.10.2](/python/docs/reference/dataplex/2.10.2/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [2.9.0](/python/docs/reference/dataplex/2.9.0/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [2.8.0](/python/docs/reference/dataplex/2.8.0/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [2.7.1](/python/docs/reference/dataplex/2.7.1/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [2.6.0](/python/docs/reference/dataplex/2.6.0/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [2.5.0](/python/docs/reference/dataplex/2.5.0/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [2.4.0](/python/docs/reference/dataplex/2.4.0/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [2.3.1](/python/docs/reference/dataplex/2.3.1/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [2.2.2](/python/docs/reference/dataplex/2.2.2/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [2.1.0](/python/docs/reference/dataplex/2.1.0/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [2.0.1](/python/docs/reference/dataplex/2.0.1/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [1.13.0](/python/docs/reference/dataplex/1.13.0/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [1.12.3](/python/docs/reference/dataplex/1.12.3/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [1.11.0](/python/docs/reference/dataplex/1.11.0/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [1.10.0](/python/docs/reference/dataplex/1.10.0/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [1.9.0](/python/docs/reference/dataplex/1.9.0/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [1.8.1](/python/docs/reference/dataplex/1.8.1/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [1.7.0](/python/docs/reference/dataplex/1.7.0/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [1.6.2](/python/docs/reference/dataplex/1.6.2/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [1.5.1](/python/docs/reference/dataplex/1.5.1/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [1.4.3](/python/docs/reference/dataplex/1.4.3/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [1.3.0](/python/docs/reference/dataplex/1.3.0/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [1.2.0](/python/docs/reference/dataplex/1.2.0/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [1.1.3](/python/docs/reference/dataplex/1.1.3/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [1.0.1](/python/docs/reference/dataplex/1.0.1/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [0.2.1](/python/docs/reference/dataplex/0.2.1/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec)\n- [0.1.0](/python/docs/reference/dataplex/0.1.0/google.cloud.dataplex_v1.types.MetadataJob.ImportJobSpec) \n\n ImportJobSpec(mapping=None, *, ignore_unknown_fields=False, **kwargs)\n\nJob specification for a metadata import job.\n\nYou can run the following kinds of metadata import jobs:\n\n- Full sync of entries with incremental import of their aspects. Supported for custom entries.\n- Incremental import of aspects only. Supported for aspects that belong to custom entries and system entries. For custom entries, you can modify both optional aspects and required aspects. For system entries, you can modify optional aspects.\n\nClasses\n-------\n\n### ImportJobScope\n\n ImportJobScope(mapping=None, *, ignore_unknown_fields=False, **kwargs)\n\nA boundary on the scope of impact that the metadata import\njob can have.\n\n### LogLevel\n\n LogLevel(value)\n\nThe level of logs to write to Cloud Logging for this job. \n\n Depending on the size of your metadata job and the number of\n logs that are generated, debug-level logging might incur\n `additional\n costs \u003chttps://cloud.google.com/stackdriver/pricing\u003e`__.\n INFO (2):\n Info-level logging. Captures logs at the\n overall job level. Includes aggregate logs about\n import items, but doesn't specify which import\n item has an error.\n\n### SyncMode\n\n SyncMode(value)\n\nSpecifies how the entries and aspects in a metadata import job are\nupdated. For more information, see `Sync\nmode \u003chttps://cloud.google.com/dataplex/docs/import-metadata#sync-mode\u003e`__. \n\n This sync mode is supported for entries.\n INCREMENTAL (2):\n Only the resources that are explicitly\n included in the metadata import file are\n modified. Use this mode to modify a subset of\n resources while leaving unreferenced resources\n unchanged.\n\n This sync mode is supported for aspects.\n NONE (3):\n If entry sync mode is `NONE`, then aspects are modified\n according to the aspect sync mode. Other metadata that\n belongs to entries in the job's scope isn't modified.\n\n This sync mode is supported for entries."]]