Package com.google.cloud.dataplex.v1

Class ImportItem.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderT>
com.google.protobuf.GeneratedMessage.Builder<ImportItem.Builder>
com.google.cloud.dataplex.v1.ImportItem.Builder
All Implemented Interfaces:
ImportItemOrBuilder, com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, Cloneable
Enclosing class:
ImportItem
public static final class ImportItem.Builder extends com.google.protobuf.GeneratedMessage.Builder<ImportItem.Builder> implements ImportItemOrBuilder
 An object that describes the values that you want to set for an entry and its
 attached aspects when you import metadata. Used when you run a metadata
 import job. See
 [CreateMetadataJob][google.cloud.dataplex.v1.CatalogService.CreateMetadataJob].

 You provide a collection of import items in a metadata import file. For more
 information about how to create a metadata import file, see [Metadata import
 file](https://cloud.google.com/dataplex/docs/import-metadata#metadata-import-file).
Protobuf type google.cloud.dataplex.v1.ImportItem

  • Method Details

    • getDescriptor

      public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()

    • internalGetFieldAccessorTable

      protected com.google.protobuf.GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()
      Specified by:
      internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessage.Builder<ImportItem.Builder>

    • clear

      public ImportItem.Builder clear()
      Specified by:
      clear in interface com.google.protobuf.Message.Builder
      Specified by:
      clear in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      clear in class com.google.protobuf.GeneratedMessage.Builder<ImportItem.Builder>

    • getDescriptorForType

      public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
      Specified by:
      getDescriptorForType in interface com.google.protobuf.Message.Builder
      Specified by:
      getDescriptorForType in interface com.google.protobuf.MessageOrBuilder
      Overrides:
      getDescriptorForType in class com.google.protobuf.GeneratedMessage.Builder<ImportItem.Builder>

    • getDefaultInstanceForType

      public ImportItem getDefaultInstanceForType()
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder

    • build

      public ImportItem build()
      Specified by:
      build in interface com.google.protobuf.Message.Builder
      Specified by:
      build in interface com.google.protobuf.MessageLite.Builder

    • buildPartial

      public ImportItem buildPartial()
      Specified by:
      buildPartial in interface com.google.protobuf.Message.Builder
      Specified by:
      buildPartial in interface com.google.protobuf.MessageLite.Builder

    • mergeFrom

      public ImportItem.Builder mergeFrom(com.google.protobuf.Message other)
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<ImportItem.Builder>

    • mergeFrom

      public ImportItem.Builder mergeFrom(ImportItem other)

    • isInitialized

      public final boolean isInitialized()
      Specified by:
      isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
      Overrides:
      isInitialized in class com.google.protobuf.GeneratedMessage.Builder<ImportItem.Builder>

    • mergeFrom

      public ImportItem.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Specified by:
      mergeFrom in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<ImportItem.Builder>
      Throws:
      IOException

    • hasEntry

      public boolean hasEntry()
       Information about an entry and its attached aspects.
      .google.cloud.dataplex.v1.Entry entry = 1;
      Specified by:
      hasEntry in interface ImportItemOrBuilder
      Returns:
      Whether the entry field is set.

    • getEntry

      public Entry getEntry()
       Information about an entry and its attached aspects.
      .google.cloud.dataplex.v1.Entry entry = 1;
      Specified by:
      getEntry in interface ImportItemOrBuilder
      Returns:
      The entry.

    • setEntry

      public ImportItem.Builder setEntry(Entry value)
       Information about an entry and its attached aspects.
      .google.cloud.dataplex.v1.Entry entry = 1;

    • setEntry

      public ImportItem.Builder setEntry(Entry.Builder builderForValue)
       Information about an entry and its attached aspects.
      .google.cloud.dataplex.v1.Entry entry = 1;

    • mergeEntry

      public ImportItem.Builder mergeEntry(Entry value)
       Information about an entry and its attached aspects.
      .google.cloud.dataplex.v1.Entry entry = 1;

    • clearEntry

      public ImportItem.Builder clearEntry()
       Information about an entry and its attached aspects.
      .google.cloud.dataplex.v1.Entry entry = 1;

    • getEntryBuilder

      public Entry.Builder getEntryBuilder()
       Information about an entry and its attached aspects.
      .google.cloud.dataplex.v1.Entry entry = 1;

    • getEntryOrBuilder

      public EntryOrBuilder getEntryOrBuilder()
       Information about an entry and its attached aspects.
      .google.cloud.dataplex.v1.Entry entry = 1;
      Specified by:
      getEntryOrBuilder in interface ImportItemOrBuilder

    • hasEntryLink

      public boolean hasEntryLink()
       Information about the entry link. User should provide either one of the
 entry or entry_link. While providing entry_link, user should not
 provide update_mask and aspect_keys.
      .google.cloud.dataplex.v1.EntryLink entry_link = 4;
      Specified by:
      hasEntryLink in interface ImportItemOrBuilder
      Returns:
      Whether the entryLink field is set.

    • getEntryLink

      public EntryLink getEntryLink()
       Information about the entry link. User should provide either one of the
 entry or entry_link. While providing entry_link, user should not
 provide update_mask and aspect_keys.
      .google.cloud.dataplex.v1.EntryLink entry_link = 4;
      Specified by:
      getEntryLink in interface ImportItemOrBuilder
      Returns:
      The entryLink.

    • setEntryLink

      public ImportItem.Builder setEntryLink(EntryLink value)
       Information about the entry link. User should provide either one of the
 entry or entry_link. While providing entry_link, user should not
 provide update_mask and aspect_keys.
      .google.cloud.dataplex.v1.EntryLink entry_link = 4;

    • setEntryLink

      public ImportItem.Builder setEntryLink(EntryLink.Builder builderForValue)
       Information about the entry link. User should provide either one of the
 entry or entry_link. While providing entry_link, user should not
 provide update_mask and aspect_keys.
      .google.cloud.dataplex.v1.EntryLink entry_link = 4;

    • mergeEntryLink

      public ImportItem.Builder mergeEntryLink(EntryLink value)
       Information about the entry link. User should provide either one of the
 entry or entry_link. While providing entry_link, user should not
 provide update_mask and aspect_keys.
      .google.cloud.dataplex.v1.EntryLink entry_link = 4;

    • clearEntryLink

      public ImportItem.Builder clearEntryLink()
       Information about the entry link. User should provide either one of the
 entry or entry_link. While providing entry_link, user should not
 provide update_mask and aspect_keys.
      .google.cloud.dataplex.v1.EntryLink entry_link = 4;

    • getEntryLinkBuilder

      public EntryLink.Builder getEntryLinkBuilder()
       Information about the entry link. User should provide either one of the
 entry or entry_link. While providing entry_link, user should not
 provide update_mask and aspect_keys.
      .google.cloud.dataplex.v1.EntryLink entry_link = 4;

    • getEntryLinkOrBuilder

      public EntryLinkOrBuilder getEntryLinkOrBuilder()
       Information about the entry link. User should provide either one of the
 entry or entry_link. While providing entry_link, user should not
 provide update_mask and aspect_keys.
      .google.cloud.dataplex.v1.EntryLink entry_link = 4;
      Specified by:
      getEntryLinkOrBuilder in interface ImportItemOrBuilder

    • hasUpdateMask

      public boolean hasUpdateMask()
       The fields to update, in paths that are relative to the `Entry` resource.
 Separate each field with a comma.

 In `FULL` entry sync mode, Dataplex Universal Catalog includes the paths of
 all of the fields for an entry that can be modified, including aspects.
 This means that Dataplex Universal Catalog replaces the existing entry with
 the entry in the metadata import file. All modifiable fields are updated,
 regardless of the fields that are listed in the update mask, and regardless
 of whether a field is present in the `entry` object.

 The `update_mask` field is ignored when an entry is created or re-created.

 In an aspect-only metadata job (when entry sync mode is `NONE`), set this
 value to `aspects`.


 Dataplex Universal Catalog also determines which entries and aspects to
 modify by comparing the values and timestamps that you provide in the
 metadata import file with the values and timestamps that exist in your
 project. For more information, see [Comparison
 logic](https://cloud.google.com/dataplex/docs/import-metadata#data-modification-logic).
      .google.protobuf.FieldMask update_mask = 2;
      Specified by:
      hasUpdateMask in interface ImportItemOrBuilder
      Returns:
      Whether the updateMask field is set.

    • getUpdateMask

      public com.google.protobuf.FieldMask getUpdateMask()
       The fields to update, in paths that are relative to the `Entry` resource.
 Separate each field with a comma.

 In `FULL` entry sync mode, Dataplex Universal Catalog includes the paths of
 all of the fields for an entry that can be modified, including aspects.
 This means that Dataplex Universal Catalog replaces the existing entry with
 the entry in the metadata import file. All modifiable fields are updated,
 regardless of the fields that are listed in the update mask, and regardless
 of whether a field is present in the `entry` object.

 The `update_mask` field is ignored when an entry is created or re-created.

 In an aspect-only metadata job (when entry sync mode is `NONE`), set this
 value to `aspects`.


 Dataplex Universal Catalog also determines which entries and aspects to
 modify by comparing the values and timestamps that you provide in the
 metadata import file with the values and timestamps that exist in your
 project. For more information, see [Comparison
 logic](https://cloud.google.com/dataplex/docs/import-metadata#data-modification-logic).
      .google.protobuf.FieldMask update_mask = 2;
      Specified by:
      getUpdateMask in interface ImportItemOrBuilder
      Returns:
      The updateMask.

    • setUpdateMask

      public ImportItem.Builder setUpdateMask(com.google.protobuf.FieldMask value)
       The fields to update, in paths that are relative to the `Entry` resource.
 Separate each field with a comma.

 In `FULL` entry sync mode, Dataplex Universal Catalog includes the paths of
 all of the fields for an entry that can be modified, including aspects.
 This means that Dataplex Universal Catalog replaces the existing entry with
 the entry in the metadata import file. All modifiable fields are updated,
 regardless of the fields that are listed in the update mask, and regardless
 of whether a field is present in the `entry` object.

 The `update_mask` field is ignored when an entry is created or re-created.

 In an aspect-only metadata job (when entry sync mode is `NONE`), set this
 value to `aspects`.


 Dataplex Universal Catalog also determines which entries and aspects to
 modify by comparing the values and timestamps that you provide in the
 metadata import file with the values and timestamps that exist in your
 project. For more information, see [Comparison
 logic](https://cloud.google.com/dataplex/docs/import-metadata#data-modification-logic).
      .google.protobuf.FieldMask update_mask = 2;

    • setUpdateMask

      public ImportItem.Builder setUpdateMask(com.google.protobuf.FieldMask.Builder builderForValue)
       The fields to update, in paths that are relative to the `Entry` resource.
 Separate each field with a comma.

 In `FULL` entry sync mode, Dataplex Universal Catalog includes the paths of
 all of the fields for an entry that can be modified, including aspects.
 This means that Dataplex Universal Catalog replaces the existing entry with
 the entry in the metadata import file. All modifiable fields are updated,
 regardless of the fields that are listed in the update mask, and regardless
 of whether a field is present in the `entry` object.

 The `update_mask` field is ignored when an entry is created or re-created.

 In an aspect-only metadata job (when entry sync mode is `NONE`), set this
 value to `aspects`.


 Dataplex Universal Catalog also determines which entries and aspects to
 modify by comparing the values and timestamps that you provide in the
 metadata import file with the values and timestamps that exist in your
 project. For more information, see [Comparison
 logic](https://cloud.google.com/dataplex/docs/import-metadata#data-modification-logic).
      .google.protobuf.FieldMask update_mask = 2;

    • mergeUpdateMask

      public ImportItem.Builder mergeUpdateMask(com.google.protobuf.FieldMask value)
       The fields to update, in paths that are relative to the `Entry` resource.
 Separate each field with a comma.

 In `FULL` entry sync mode, Dataplex Universal Catalog includes the paths of
 all of the fields for an entry that can be modified, including aspects.
 This means that Dataplex Universal Catalog replaces the existing entry with
 the entry in the metadata import file. All modifiable fields are updated,
 regardless of the fields that are listed in the update mask, and regardless
 of whether a field is present in the `entry` object.

 The `update_mask` field is ignored when an entry is created or re-created.

 In an aspect-only metadata job (when entry sync mode is `NONE`), set this
 value to `aspects`.


 Dataplex Universal Catalog also determines which entries and aspects to
 modify by comparing the values and timestamps that you provide in the
 metadata import file with the values and timestamps that exist in your
 project. For more information, see [Comparison
 logic](https://cloud.google.com/dataplex/docs/import-metadata#data-modification-logic).
      .google.protobuf.FieldMask update_mask = 2;

    • clearUpdateMask

      public ImportItem.Builder clearUpdateMask()
       The fields to update, in paths that are relative to the `Entry` resource.
 Separate each field with a comma.

 In `FULL` entry sync mode, Dataplex Universal Catalog includes the paths of
 all of the fields for an entry that can be modified, including aspects.
 This means that Dataplex Universal Catalog replaces the existing entry with
 the entry in the metadata import file. All modifiable fields are updated,
 regardless of the fields that are listed in the update mask, and regardless
 of whether a field is present in the `entry` object.

 The `update_mask` field is ignored when an entry is created or re-created.

 In an aspect-only metadata job (when entry sync mode is `NONE`), set this
 value to `aspects`.


 Dataplex Universal Catalog also determines which entries and aspects to
 modify by comparing the values and timestamps that you provide in the
 metadata import file with the values and timestamps that exist in your
 project. For more information, see [Comparison
 logic](https://cloud.google.com/dataplex/docs/import-metadata#data-modification-logic).
      .google.protobuf.FieldMask update_mask = 2;

    • getUpdateMaskBuilder

      public com.google.protobuf.FieldMask.Builder getUpdateMaskBuilder()
       The fields to update, in paths that are relative to the `Entry` resource.
 Separate each field with a comma.

 In `FULL` entry sync mode, Dataplex Universal Catalog includes the paths of
 all of the fields for an entry that can be modified, including aspects.
 This means that Dataplex Universal Catalog replaces the existing entry with
 the entry in the metadata import file. All modifiable fields are updated,
 regardless of the fields that are listed in the update mask, and regardless
 of whether a field is present in the `entry` object.

 The `update_mask` field is ignored when an entry is created or re-created.

 In an aspect-only metadata job (when entry sync mode is `NONE`), set this
 value to `aspects`.


 Dataplex Universal Catalog also determines which entries and aspects to
 modify by comparing the values and timestamps that you provide in the
 metadata import file with the values and timestamps that exist in your
 project. For more information, see [Comparison
 logic](https://cloud.google.com/dataplex/docs/import-metadata#data-modification-logic).
      .google.protobuf.FieldMask update_mask = 2;

    • getUpdateMaskOrBuilder

      public com.google.protobuf.FieldMaskOrBuilder getUpdateMaskOrBuilder()
       The fields to update, in paths that are relative to the `Entry` resource.
 Separate each field with a comma.

 In `FULL` entry sync mode, Dataplex Universal Catalog includes the paths of
 all of the fields for an entry that can be modified, including aspects.
 This means that Dataplex Universal Catalog replaces the existing entry with
 the entry in the metadata import file. All modifiable fields are updated,
 regardless of the fields that are listed in the update mask, and regardless
 of whether a field is present in the `entry` object.

 The `update_mask` field is ignored when an entry is created or re-created.

 In an aspect-only metadata job (when entry sync mode is `NONE`), set this
 value to `aspects`.


 Dataplex Universal Catalog also determines which entries and aspects to
 modify by comparing the values and timestamps that you provide in the
 metadata import file with the values and timestamps that exist in your
 project. For more information, see [Comparison
 logic](https://cloud.google.com/dataplex/docs/import-metadata#data-modification-logic).
      .google.protobuf.FieldMask update_mask = 2;
      Specified by:
      getUpdateMaskOrBuilder in interface ImportItemOrBuilder

    • getAspectKeysList

      public com.google.protobuf.ProtocolStringList getAspectKeysList()
       The aspects to modify. Supports the following syntaxes:

 * `{aspect_type_reference}`: matches aspects that belong to the specified
 aspect type and are attached directly to the entry.
 * `{aspect_type_reference}@{path}`: matches aspects that belong to the
 specified aspect type and path.
 * `{aspect_type_reference}@*` : matches aspects of the given type for all
 paths.
 * `*@path` : matches aspects of all types on the given path.

 Replace `{aspect_type_reference}` with a reference to the aspect type, in
 the format
 `{project_id_or_number}.{location_id}.{aspect_type_id}`.

 In `FULL` entry sync mode, if you leave this field empty, it is treated as
 specifying exactly those aspects that are present within the specified
 entry. Dataplex Universal Catalog implicitly adds the keys for all of the
 required aspects of an entry.
      repeated string aspect_keys = 3;
      Specified by:
      getAspectKeysList in interface ImportItemOrBuilder
      Returns:
      A list containing the aspectKeys.

    • getAspectKeysCount

      public int getAspectKeysCount()
       The aspects to modify. Supports the following syntaxes:

 * `{aspect_type_reference}`: matches aspects that belong to the specified
 aspect type and are attached directly to the entry.
 * `{aspect_type_reference}@{path}`: matches aspects that belong to the
 specified aspect type and path.
 * `{aspect_type_reference}@*` : matches aspects of the given type for all
 paths.
 * `*@path` : matches aspects of all types on the given path.

 Replace `{aspect_type_reference}` with a reference to the aspect type, in
 the format
 `{project_id_or_number}.{location_id}.{aspect_type_id}`.

 In `FULL` entry sync mode, if you leave this field empty, it is treated as
 specifying exactly those aspects that are present within the specified
 entry. Dataplex Universal Catalog implicitly adds the keys for all of the
 required aspects of an entry.
      repeated string aspect_keys = 3;
      Specified by:
      getAspectKeysCount in interface ImportItemOrBuilder
      Returns:
      The count of aspectKeys.

    • getAspectKeys

      public String getAspectKeys(int index)
       The aspects to modify. Supports the following syntaxes:

 * `{aspect_type_reference}`: matches aspects that belong to the specified
 aspect type and are attached directly to the entry.
 * `{aspect_type_reference}@{path}`: matches aspects that belong to the
 specified aspect type and path.
 * `{aspect_type_reference}@*` : matches aspects of the given type for all
 paths.
 * `*@path` : matches aspects of all types on the given path.

 Replace `{aspect_type_reference}` with a reference to the aspect type, in
 the format
 `{project_id_or_number}.{location_id}.{aspect_type_id}`.

 In `FULL` entry sync mode, if you leave this field empty, it is treated as
 specifying exactly those aspects that are present within the specified
 entry. Dataplex Universal Catalog implicitly adds the keys for all of the
 required aspects of an entry.
      repeated string aspect_keys = 3;
      Specified by:
      getAspectKeys in interface ImportItemOrBuilder
      Parameters:
      index - The index of the element to return.
      Returns:
      The aspectKeys at the given index.

    • getAspectKeysBytes

      public com.google.protobuf.ByteString getAspectKeysBytes(int index)
       The aspects to modify. Supports the following syntaxes:

 * `{aspect_type_reference}`: matches aspects that belong to the specified
 aspect type and are attached directly to the entry.
 * `{aspect_type_reference}@{path}`: matches aspects that belong to the
 specified aspect type and path.
 * `{aspect_type_reference}@*` : matches aspects of the given type for all
 paths.
 * `*@path` : matches aspects of all types on the given path.

 Replace `{aspect_type_reference}` with a reference to the aspect type, in
 the format
 `{project_id_or_number}.{location_id}.{aspect_type_id}`.

 In `FULL` entry sync mode, if you leave this field empty, it is treated as
 specifying exactly those aspects that are present within the specified
 entry. Dataplex Universal Catalog implicitly adds the keys for all of the
 required aspects of an entry.
      repeated string aspect_keys = 3;
      Specified by:
      getAspectKeysBytes in interface ImportItemOrBuilder
      Parameters:
      index - The index of the value to return.
      Returns:
      The bytes of the aspectKeys at the given index.

    • setAspectKeys

      public ImportItem.Builder setAspectKeys(int index, String value)
       The aspects to modify. Supports the following syntaxes:

 * `{aspect_type_reference}`: matches aspects that belong to the specified
 aspect type and are attached directly to the entry.
 * `{aspect_type_reference}@{path}`: matches aspects that belong to the
 specified aspect type and path.
 * `{aspect_type_reference}@*` : matches aspects of the given type for all
 paths.
 * `*@path` : matches aspects of all types on the given path.

 Replace `{aspect_type_reference}` with a reference to the aspect type, in
 the format
 `{project_id_or_number}.{location_id}.{aspect_type_id}`.

 In `FULL` entry sync mode, if you leave this field empty, it is treated as
 specifying exactly those aspects that are present within the specified
 entry. Dataplex Universal Catalog implicitly adds the keys for all of the
 required aspects of an entry.
      repeated string aspect_keys = 3;
      Parameters:
      index - The index to set the value at.
      value - The aspectKeys to set.
      Returns:
      This builder for chaining.

    • addAspectKeys

      public ImportItem.Builder addAspectKeys(String value)
       The aspects to modify. Supports the following syntaxes:

 * `{aspect_type_reference}`: matches aspects that belong to the specified
 aspect type and are attached directly to the entry.
 * `{aspect_type_reference}@{path}`: matches aspects that belong to the
 specified aspect type and path.
 * `{aspect_type_reference}@*` : matches aspects of the given type for all
 paths.
 * `*@path` : matches aspects of all types on the given path.

 Replace `{aspect_type_reference}` with a reference to the aspect type, in
 the format
 `{project_id_or_number}.{location_id}.{aspect_type_id}`.

 In `FULL` entry sync mode, if you leave this field empty, it is treated as
 specifying exactly those aspects that are present within the specified
 entry. Dataplex Universal Catalog implicitly adds the keys for all of the
 required aspects of an entry.
      repeated string aspect_keys = 3;
      Parameters:
      value - The aspectKeys to add.
      Returns:
      This builder for chaining.

    • addAllAspectKeys

      public ImportItem.Builder addAllAspectKeys(Iterable<String> values)
       The aspects to modify. Supports the following syntaxes:

 * `{aspect_type_reference}`: matches aspects that belong to the specified
 aspect type and are attached directly to the entry.
 * `{aspect_type_reference}@{path}`: matches aspects that belong to the
 specified aspect type and path.
 * `{aspect_type_reference}@*` : matches aspects of the given type for all
 paths.
 * `*@path` : matches aspects of all types on the given path.

 Replace `{aspect_type_reference}` with a reference to the aspect type, in
 the format
 `{project_id_or_number}.{location_id}.{aspect_type_id}`.

 In `FULL` entry sync mode, if you leave this field empty, it is treated as
 specifying exactly those aspects that are present within the specified
 entry. Dataplex Universal Catalog implicitly adds the keys for all of the
 required aspects of an entry.
      repeated string aspect_keys = 3;
      Parameters:
      values - The aspectKeys to add.
      Returns:
      This builder for chaining.

    • clearAspectKeys

      public ImportItem.Builder clearAspectKeys()
       The aspects to modify. Supports the following syntaxes:

 * `{aspect_type_reference}`: matches aspects that belong to the specified
 aspect type and are attached directly to the entry.
 * `{aspect_type_reference}@{path}`: matches aspects that belong to the
 specified aspect type and path.
 * `{aspect_type_reference}@*` : matches aspects of the given type for all
 paths.
 * `*@path` : matches aspects of all types on the given path.

 Replace `{aspect_type_reference}` with a reference to the aspect type, in
 the format
 `{project_id_or_number}.{location_id}.{aspect_type_id}`.

 In `FULL` entry sync mode, if you leave this field empty, it is treated as
 specifying exactly those aspects that are present within the specified
 entry. Dataplex Universal Catalog implicitly adds the keys for all of the
 required aspects of an entry.
      repeated string aspect_keys = 3;
      Returns:
      This builder for chaining.

    • addAspectKeysBytes

      public ImportItem.Builder addAspectKeysBytes(com.google.protobuf.ByteString value)
       The aspects to modify. Supports the following syntaxes:

 * `{aspect_type_reference}`: matches aspects that belong to the specified
 aspect type and are attached directly to the entry.
 * `{aspect_type_reference}@{path}`: matches aspects that belong to the
 specified aspect type and path.
 * `{aspect_type_reference}@*` : matches aspects of the given type for all
 paths.
 * `*@path` : matches aspects of all types on the given path.

 Replace `{aspect_type_reference}` with a reference to the aspect type, in
 the format
 `{project_id_or_number}.{location_id}.{aspect_type_id}`.

 In `FULL` entry sync mode, if you leave this field empty, it is treated as
 specifying exactly those aspects that are present within the specified
 entry. Dataplex Universal Catalog implicitly adds the keys for all of the
 required aspects of an entry.
      repeated string aspect_keys = 3;
      Parameters:
      value - The bytes of the aspectKeys to add.
      Returns:
      This builder for chaining.