Method: projects.locations.entryGroups.entries.patch

Updates an existing entry. Users should enable the Data Catalog API in the project identified by the parameter (see Data Catalog Resource Project for more information).

HTTP request


Path parameters



Output only. The Data Catalog resource name of the entry in URL format. Example:

  • projects/{projectId}/locations/{location}/entryGroups/{entryGroupId}/entries/{entryId}

Note that this Entry and its child resources may not actually be stored in the location in this name. It takes the form projects/{project}/locations/{location}/entryGroups/{entrygroup}/entries/{entries}.

Query parameters


string (FieldMask format)

Names of fields whose values to overwrite on an entry.

If this parameter is absent or empty, all modifiable fields are overwritten. If such fields are non-required and omitted in the request body, their values are emptied.

The following fields are modifiable:

  • For entries with type DATA_STREAM:
  • schema
  • For entries with type FILESET:
  • schema
  • displayName
  • description
  • gcsFilesetSpec
  • gcsFilesetSpec.file_patterns
  • For entries with userSpecifiedType:
  • schema
  • displayName
  • description
  • userSpecifiedType
  • userSpecifiedSystem
  • linkedResource
  • sourceSystemTimestamps

This is a comma-separated list of fully qualified names of fields. Example: "user.displayName,photo".

Request body

The request body contains an instance of Entry.

Response body

If successful, the response body contains an instance of Entry.

Authorization scopes

Requires the following OAuth scope:


For more information, see the Authentication Overview.