Optional. Mask of fields to update. To update Aspects, the update_mask must contain the value "aspects". If the update_mask is empty, the service will update all modifiable fields present in the request.
↳ allow_missing
bool
Optional. If set to true and the entry doesn't exist, the service will create it.
↳ delete_missing_aspects
bool
Optional. If set to true and the aspect_keys specify aspect ranges, the service deletes any existing aspects from that range that weren't provided in the request.
↳ aspect_keys
array
Optional. The map keys of the Aspects which the service should modify. It supports the following syntaxes: * *<aspect_type_reference>- matches an aspect of the given type and empty path. * *<aspect_type_reference>@path- matches an aspect of the given type and specified path. For example, to attach an aspect to a field that is specified by theschemaaspect, the path should have the formatSchema.<field_name>. * *<aspect_type_reference>@*- matches aspects of the given type for all paths. * **@path- matches aspects of all types on the given path. The service will not remove existing aspects matching the syntax unlessdelete_missing_aspectsis set to true. If this field is left empty, the service treats it as specifying exactly those Aspects present in the request.
Optional. If set to true and the entry doesn't exist, the service will
create it.
Returns
Type
Description
bool
setAllowMissing
Optional. If set to true and the entry doesn't exist, the service will
create it.
Parameter
Name
Description
var
bool
Returns
Type
Description
$this
getDeleteMissingAspects
Optional. If set to true and the aspect_keys specify aspect ranges, the
service deletes any existing aspects from that range that weren't provided
in the request.
Returns
Type
Description
bool
setDeleteMissingAspects
Optional. If set to true and the aspect_keys specify aspect ranges, the
service deletes any existing aspects from that range that weren't provided
in the request.
Parameter
Name
Description
var
bool
Returns
Type
Description
$this
getAspectKeys
Optional. The map keys of the Aspects which the service should modify. It
supports the following syntaxes:
<aspect_type_reference>- matches an aspect of the given type and empty
path.
<aspect_type_reference>@path- matches an aspect of the given type and
specified path. For example, to attach an aspect to a field that is
specified by theschemaaspect, the path should have the formatSchema.<field_name>.
<aspect_type_reference>@*- matches aspects of the given type for all
paths.
*@path- matches aspects of all types on the given path.
The service will not remove existing aspects matching the syntax unlessdelete_missing_aspectsis set to true.
If this field is left empty, the service treats it as specifying
exactly those Aspects present in the request.
Optional. The map keys of the Aspects which the service should modify. It
supports the following syntaxes:
<aspect_type_reference>- matches an aspect of the given type and empty
path.
<aspect_type_reference>@path- matches an aspect of the given type and
specified path. For example, to attach an aspect to a field that is
specified by theschemaaspect, the path should have the formatSchema.<field_name>.
<aspect_type_reference>@*- matches aspects of the given type for all
paths.
*@path- matches aspects of all types on the given path.
The service will not remove existing aspects matching the syntax unlessdelete_missing_aspectsis set to true.
If this field is left empty, the service treats it as specifying
exactly those Aspects present in the request.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Google Cloud Dataplex V1 Client - Class UpdateEntryRequest (1.7.1)\n\nVersion latestkeyboard_arrow_down\n\n- [1.7.1 (latest)](/php/docs/reference/cloud-dataplex/latest/V1.UpdateEntryRequest)\n- [1.7.0](/php/docs/reference/cloud-dataplex/1.7.0/V1.UpdateEntryRequest)\n- [1.6.1](/php/docs/reference/cloud-dataplex/1.6.1/V1.UpdateEntryRequest)\n- [1.4.0](/php/docs/reference/cloud-dataplex/1.4.0/V1.UpdateEntryRequest)\n- [1.3.0](/php/docs/reference/cloud-dataplex/1.3.0/V1.UpdateEntryRequest)\n- [1.2.1](/php/docs/reference/cloud-dataplex/1.2.1/V1.UpdateEntryRequest)\n- [1.1.1](/php/docs/reference/cloud-dataplex/1.1.1/V1.UpdateEntryRequest)\n- [1.0.1](/php/docs/reference/cloud-dataplex/1.0.1/V1.UpdateEntryRequest)\n- [0.16.1](/php/docs/reference/cloud-dataplex/0.16.1/V1.UpdateEntryRequest)\n- [0.15.1](/php/docs/reference/cloud-dataplex/0.15.1/V1.UpdateEntryRequest)\n- [0.14.0](/php/docs/reference/cloud-dataplex/0.14.0/V1.UpdateEntryRequest)\n- [0.13.0](/php/docs/reference/cloud-dataplex/0.13.0/V1.UpdateEntryRequest)\n- [0.12.0](/php/docs/reference/cloud-dataplex/0.12.0/V1.UpdateEntryRequest)\n- [0.11.1](/php/docs/reference/cloud-dataplex/0.11.1/V1.UpdateEntryRequest)\n- [0.10.0](/php/docs/reference/cloud-dataplex/0.10.0/V1.UpdateEntryRequest)\n- [0.9.0](/php/docs/reference/cloud-dataplex/0.9.0/V1.UpdateEntryRequest)\n- [0.8.0](/php/docs/reference/cloud-dataplex/0.8.0/V1.UpdateEntryRequest)\n- [0.7.0](/php/docs/reference/cloud-dataplex/0.7.0/V1.UpdateEntryRequest)\n- [0.6.0](/php/docs/reference/cloud-dataplex/0.6.0/V1.UpdateEntryRequest)\n- [0.5.1](/php/docs/reference/cloud-dataplex/0.5.1/V1.UpdateEntryRequest)\n- [0.4.0](/php/docs/reference/cloud-dataplex/0.4.0/V1.UpdateEntryRequest)\n- [0.3.0](/php/docs/reference/cloud-dataplex/0.3.0/V1.UpdateEntryRequest)\n- [0.2.3](/php/docs/reference/cloud-dataplex/0.2.3/V1.UpdateEntryRequest)\n- [0.1.6](/php/docs/reference/cloud-dataplex/0.1.6/V1.UpdateEntryRequest) \nReference documentation and code samples for the Google Cloud Dataplex V1 Client class UpdateEntryRequest.\n\nUpdate Entry request.\n\nGenerated from protobuf message `google.cloud.dataplex.v1.UpdateEntryRequest`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ Dataplex \\\\ V1\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getEntry\n\nRequired. Entry resource.\n\n### hasEntry\n\n### clearEntry\n\n### setEntry\n\nRequired. Entry resource.\n\n### getUpdateMask\n\nOptional. Mask of fields to update. To update Aspects, the update_mask must\ncontain the value \"aspects\".\n\nIf the update_mask is empty, the service will update all modifiable fields\npresent in the request.\n\n### hasUpdateMask\n\n### clearUpdateMask\n\n### setUpdateMask\n\nOptional. Mask of fields to update. To update Aspects, the update_mask must\ncontain the value \"aspects\".\n\nIf the update_mask is empty, the service will update all modifiable fields\npresent in the request.\n\n### getAllowMissing\n\nOptional. If set to true and the entry doesn't exist, the service will\ncreate it.\n\n### setAllowMissing\n\nOptional. If set to true and the entry doesn't exist, the service will\ncreate it.\n\n### getDeleteMissingAspects\n\nOptional. If set to true and the aspect_keys specify aspect ranges, the\nservice deletes any existing aspects from that range that weren't provided\nin the request.\n\n### setDeleteMissingAspects\n\nOptional. If set to true and the aspect_keys specify aspect ranges, the\nservice deletes any existing aspects from that range that weren't provided\nin the request.\n\n### getAspectKeys\n\nOptional. The map keys of the Aspects which the service should modify. It\nsupports the following syntaxes:\n\n- `\u003caspect_type_reference\u003e` - matches an aspect of the given type and empty\n path.\n\n- `\u003caspect_type_reference\u003e@path` - matches an aspect of the given type and\n specified path. For example, to attach an aspect to a field that is\n specified by the `schema` aspect, the path should have the format\n `Schema.\u003cfield_name\u003e`.\n\n- `\u003caspect_type_reference\u003e@*` - matches aspects of the given type for all paths.\n- `*@path` - matches aspects of all types on the given path. The service will not remove existing aspects matching the syntax unless `delete_missing_aspects` is set to true. If this field is left empty, the service treats it as specifying exactly those Aspects present in the request.\n\n### setAspectKeys\n\nOptional. The map keys of the Aspects which the service should modify. It\nsupports the following syntaxes:\n\n- `\u003caspect_type_reference\u003e` - matches an aspect of the given type and empty\n path.\n\n- `\u003caspect_type_reference\u003e@path` - matches an aspect of the given type and\n specified path. For example, to attach an aspect to a field that is\n specified by the `schema` aspect, the path should have the format\n `Schema.\u003cfield_name\u003e`.\n\n- `\u003caspect_type_reference\u003e@*` - matches aspects of the given type for all paths.\n- `*@path` - matches aspects of all types on the given path. The service will not remove existing aspects matching the syntax unless `delete_missing_aspects` is set to true. If this field is left empty, the service treats it as specifying exactly those Aspects present in the request.\n\n### static::build"]]
