Metadata about the asset, such as package, ID, release notes, etc.

The Data asset payload.

ReferencedData contained in the proto must be portable within the context in which this asset will be used. E.g.: - file references should only be used if the DataAsset will only be consumed locally; - CAS IDs must be unambiguous and the corresponding CAS document accessible to any consumer.

A complete descriptor for the data message type.

Restrict results to Data assets of the specified fully qualified proto name (without leading dot and not a type URL). For example: "intrinsic_proto.data.v1.DataAsset".

The name of the field to access.

If the field is a list, the index of the element to access.

If the field is a map, the key of the entry to access.

The ID of the Data asset to retrieve.

Maximum number of assets to return (fewer may be returned).

A page token received from a previous ListDataAssetMetadata call. Provide this token to retrieve the next page of results.

Optional filter to apply to the query to retrieve a filtered list of assets.

Pass this token to a subsequent list request to obtain the next page.

Maximum number of assets to return (fewer may be returned).

A page token received from a previous ListDataAssets call. Provide this token to retrieve the next page of results.

Optional filter to apply to the query to retrieve a filtered list of assets.

Pass this token to a subsequent list request to obtain the next page.

An optional digest of the referenced data, prefixed with the hashing algorithm (e.g., "sha256:").

Can be used to ensure that the referenced data have not changed.

If the ReferencedData references CAS data in an ambiguous context (e.g., releasing to the catalog a Data asset that references existing CAS data), then this field can be used to specify the target project for the reference.

The consumer of this reference must have access to the source project.

Not providing this value may be an error in contexts in which the target project is needed and not known otherwise.

A reference to data stored elsewhere (e.g., as a file or in content-addressable storage [CAS]).

The value is a URI to the referenced data. Can be one of the following: - a CAS ID of the form "intcas://..."; - a file path of the form "file://..."; - a file path without protocol prefix, either absolute or relative.

If a relative file path is provided, then its base path must be unambiguous in the context in which this proto is used.

The inlined data.

The ID of the installed Data asset that contains the referenced data.

The path to the ReferencedData field within the installed Data asset proto.

For example, for the following Data asset proto:

message MyData {
  message ListOfData {
    repeated ReferencedData data_list = 1;
  }
  map<string,  ListOfData> data_map = 1;
}

The path to the 2nd data_list value within the data_map entry at key "foo" would be:

field_path { field: "data_map" key: "foo" }
field_path { field: "data_list" index: 1 }

If the Data asset proto is itself a ReferencedData value, then this path is empty.

The maximum number of bytes to stream per response.

If omitted, the server will choose a sensible default value.

The ReferencedData whose data should be streamed.

File references are not valid.

The path to the ReferencedData field within an installed Data asset proto.

This option can be used to stream data from a Data asset without first retrieving the asset itself.

A chunk of data from the ReferencedData.

The total size of the referenced data.

The offset of the chunk within the referenced data.