- 1.52.0 (latest)
- 1.51.0
- 1.50.0
- 1.49.0
- 1.47.0
- 1.46.0
- 1.45.0
- 1.44.0
- 1.43.0
- 1.42.0
- 1.41.0
- 1.40.0
- 1.39.0
- 1.38.0
- 1.37.0
- 1.35.0
- 1.34.0
- 1.33.0
- 1.32.0
- 1.31.0
- 1.30.0
- 1.29.0
- 1.28.0
- 1.27.0
- 1.26.0
- 1.25.0
- 1.22.0
- 1.21.0
- 1.20.0
- 1.19.0
- 1.18.0
- 1.17.0
- 1.16.0
- 1.15.0
- 1.14.0
- 1.13.0
- 1.12.0
- 1.11.0
- 1.10.0
- 1.9.0
- 1.7.0
- 1.6.0
- 1.5.0
- 1.4.0
- 1.3.0
- 1.2.0
- 1.1.2
- 1.0.1
- 0.2.2
public interface ImportItemOrBuilder extends MessageOrBuilder
Implements
MessageOrBuilderMethods
getAspectKeys(int index)
public abstract 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 that belong to the specified aspect type for all paths.Replace
{aspect_type_reference}
with a reference to the aspect type, in the format{project_id_or_number}.{location_id}.{aspect_type_id}
.If you leave this field empty, it is treated as specifying exactly those aspects that are present within the specified entry.
In
FULL
entry sync mode, Dataplex implicitly adds the keys for all of the required aspects of an entry.
repeated string aspect_keys = 3;
Parameter | |
---|---|
Name | Description |
index |
int The index of the element to return. |
Returns | |
---|---|
Type | Description |
String |
The aspectKeys at the given index. |
getAspectKeysBytes(int index)
public abstract 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 that belong to the specified aspect type for all paths.Replace
{aspect_type_reference}
with a reference to the aspect type, in the format{project_id_or_number}.{location_id}.{aspect_type_id}
.If you leave this field empty, it is treated as specifying exactly those aspects that are present within the specified entry.
In
FULL
entry sync mode, Dataplex implicitly adds the keys for all of the required aspects of an entry.
repeated string aspect_keys = 3;
Parameter | |
---|---|
Name | Description |
index |
int The index of the value to return. |
Returns | |
---|---|
Type | Description |
ByteString |
The bytes of the aspectKeys at the given index. |
getAspectKeysCount()
public abstract 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 that belong to the specified aspect type for all paths.Replace
{aspect_type_reference}
with a reference to the aspect type, in the format{project_id_or_number}.{location_id}.{aspect_type_id}
.If you leave this field empty, it is treated as specifying exactly those aspects that are present within the specified entry.
In
FULL
entry sync mode, Dataplex implicitly adds the keys for all of the required aspects of an entry.
repeated string aspect_keys = 3;
Returns | |
---|---|
Type | Description |
int |
The count of aspectKeys. |
getAspectKeysList()
public abstract List<String> 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 that belong to the specified aspect type for all paths.Replace
{aspect_type_reference}
with a reference to the aspect type, in the format{project_id_or_number}.{location_id}.{aspect_type_id}
.If you leave this field empty, it is treated as specifying exactly those aspects that are present within the specified entry.
In
FULL
entry sync mode, Dataplex implicitly adds the keys for all of the required aspects of an entry.
repeated string aspect_keys = 3;
Returns | |
---|---|
Type | Description |
List<String> |
A list containing the aspectKeys. |
getEntry()
public abstract Entry getEntry()
Information about an entry and its attached aspects.
.google.cloud.dataplex.v1.Entry entry = 1;
Returns | |
---|---|
Type | Description |
Entry |
The entry. |
getEntryOrBuilder()
public abstract EntryOrBuilder getEntryOrBuilder()
Information about an entry and its attached aspects.
.google.cloud.dataplex.v1.Entry entry = 1;
Returns | |
---|---|
Type | Description |
EntryOrBuilder |
getUpdateMask()
public abstract 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 includes the paths of all of the fields
for an entry that can be modified, including aspects. This means that
Dataplex 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.
Dataplex 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.
.google.protobuf.FieldMask update_mask = 2;
Returns | |
---|---|
Type | Description |
FieldMask |
The updateMask. |
getUpdateMaskOrBuilder()
public abstract 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 includes the paths of all of the fields
for an entry that can be modified, including aspects. This means that
Dataplex 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.
Dataplex 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.
.google.protobuf.FieldMask update_mask = 2;
Returns | |
---|---|
Type | Description |
FieldMaskOrBuilder |
hasEntry()
public abstract boolean hasEntry()
Information about an entry and its attached aspects.
.google.cloud.dataplex.v1.Entry entry = 1;
Returns | |
---|---|
Type | Description |
boolean |
Whether the entry field is set. |
hasUpdateMask()
public abstract 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 includes the paths of all of the fields
for an entry that can be modified, including aspects. This means that
Dataplex 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.
Dataplex 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.
.google.protobuf.FieldMask update_mask = 2;
Returns | |
---|---|
Type | Description |
boolean |
Whether the updateMask field is set. |