- 1.36.0 (latest)
- 1.35.0
- 1.34.1
- 1.33.0
- 1.32.1
- 1.31.1
- 1.30.1
- 1.29.0
- 1.28.0
- 1.27.0
- 1.26.0
- 1.25.0
- 1.24.0
- 1.23.1
- 1.22.0
- 1.21.0
- 1.20.1
- 1.19.0
- 1.18.0
- 1.17.1
- 1.16.0
- 1.15.0
- 1.14.1
- 1.13.5
- 1.12.1
- 1.11.0
- 1.10.0
- 1.9.1
- 1.8.0
- 1.7.0
- 1.6.0
- 1.5.0
- 1.4.0
- 1.3.2
- 1.2.0
- 1.1.1
- 1.0.0
- 0.8.2
- 0.7.1
- 0.6.0
- 0.5.0
- 0.4.1
- 0.3.0
- 0.2.0
- 0.1.1
ImportEntityTypesRequest(mapping=None, *, ignore_unknown_fields=False, **kwargs)The request message for EntityTypes.ImportEntityTypes.
This message has oneof_ fields (mutually exclusive fields).
For each oneof, at most one member field can be set at the same time.
Setting any member of the oneof automatically clears all other
members.
.. _oneof: https://proto-plus-python.readthedocs.io/en/stable/fields.html#oneofs-mutually-exclusive-fields
Attributes |
|
|---|---|
| Name | Description |
parent |
str
Required. The agent to import the entity types into. Format: projects/.
|
entity_types_uri |
str
The `Google Cloud Storage |
entity_types_content |
google.cloud.dialogflowcx_v3.types.InlineSource
Uncompressed byte content of entity types. This field is a member of oneof_ entity_types.
|
merge_option |
google.cloud.dialogflowcx_v3.types.ImportEntityTypesRequest.MergeOption
Required. Merge option for importing entity types. |
target_entity_type |
str
Optional. The target entity type to import into. Format: projects/.
If set, there should be only one entity type included in
entity_types,
of which the type should match the type of the target entity
type. All
entities
in the imported entity type will be added to the target
entity type.
|
Classes
MergeOption
MergeOption(value)Merge option when display name conflicts exist during import.
Values: MERGE_OPTION_UNSPECIFIED (0): Unspecified. If used, system uses REPORT_CONFLICT as default. REPLACE (1): Replace the original entity type in the agent with the new entity type when display name conflicts exist. MERGE (2): Merge the original entity type with the new entity type when display name conflicts exist. RENAME (3): Create new entity types with new display names to differentiate them from the existing entity types when display name conflicts exist. REPORT_CONFLICT (4): Report conflict information if display names conflict is detected. Otherwise, import entity types. KEEP (5): Keep the original entity type and discard the conflicting new entity type when display name conflicts exist.