Generated from protobuf message google.cloud.aiplatform.v1.QueryArtifactLineageSubgraphRequest
Namespace
Google \ Cloud \ AIPlatform \ V1
Methods
__construct
Constructor.
Parameters
Name
Description
data
array
Optional. Data for populating the Message object.
↳ artifact
string
Required. The resource name of the Artifact whose Lineage needs to be retrieved as a LineageSubgraph. Format: projects/{project}/locations/{location}/metadataStores/{metadatastore}/artifacts/{artifact} The request may error with FAILED_PRECONDITION if the number of Artifacts, the number of Executions, or the number of Events that would be returned for the Context exceeds 1000.
↳ max_hops
int
Specifies the size of the lineage graph in terms of number of hops from the specified artifact. Negative Value: INVALID_ARGUMENT error is returned 0: Only input artifact is returned. No value: Transitive closure is performed to return the complete graph.
↳ filter
string
Filter specifying the boolean condition for the Artifacts to satisfy in order to be part of the Lineage Subgraph. The syntax to define filter query is based on https://google.aip.dev/160. The supported set of filters include the following: * * Attribute filtering: For example: display_name = "test" Supported fields include: name, display_name, uri, state, schema_title, create_time, and update_time. Time fields, such as create_time and update_time, require values specified in RFC-3339 format. For example: create_time = "2020-11-19T11:30:00-04:00" * * Metadata field: To filter on metadata fields use traversal operation as follows: metadata.<field_name>.<type_value>. For example: metadata.field_1.number_value = 10.0 In case the field name contains special characters (such as colon), one can embed it inside double quote. For example: metadata."field:1".number_value = 10.0 Each of the above supported filter types can be combined together using logical operators (AND & OR). Maximum nested expression depth allowed is 5. For example: display_name = "test" AND metadata.field1.bool_value = true.
getArtifact
Required. The resource name of the Artifact whose Lineage needs to be
retrieved as a LineageSubgraph. Format:
projects/{project}/locations/{location}/metadataStores/{metadatastore}/artifacts/{artifact}
The request may error with FAILED_PRECONDITION if the number of Artifacts,
the number of Executions, or the number of Events that would be returned
for the Context exceeds 1000.
Returns
Type
Description
string
setArtifact
Required. The resource name of the Artifact whose Lineage needs to be
retrieved as a LineageSubgraph. Format:
projects/{project}/locations/{location}/metadataStores/{metadatastore}/artifacts/{artifact}
The request may error with FAILED_PRECONDITION if the number of Artifacts,
the number of Executions, or the number of Events that would be returned
for the Context exceeds 1000.
Parameter
Name
Description
var
string
Returns
Type
Description
$this
getMaxHops
Specifies the size of the lineage graph in terms of number of hops from the
specified artifact.
Negative Value: INVALID_ARGUMENT error is returned
0: Only input artifact is returned.
No value: Transitive closure is performed to return the complete graph.
Returns
Type
Description
int
setMaxHops
Specifies the size of the lineage graph in terms of number of hops from the
specified artifact.
Negative Value: INVALID_ARGUMENT error is returned
0: Only input artifact is returned.
No value: Transitive closure is performed to return the complete graph.
Parameter
Name
Description
var
int
Returns
Type
Description
$this
getFilter
Filter specifying the boolean condition for the Artifacts to satisfy in
order to be part of the Lineage Subgraph.
The syntax to define filter query is based on https://google.aip.dev/160.
The supported set of filters include the following:
Attribute filtering:
For example: display_name = "test"
Supported fields include: name, display_name, uri, state,
schema_title, create_time, and update_time.
Time fields, such as create_time and update_time, require values
specified in RFC-3339 format.
For example: create_time = "2020-11-19T11:30:00-04:00"
Metadata field:
To filter on metadata fields use traversal operation as follows:
metadata.<field_name>.<type_value>.
For example: metadata.field_1.number_value = 10.0
In case the field name contains special characters (such as colon), one
can embed it inside double quote.
For example: metadata."field:1".number_value = 10.0
Each of the above supported filter types can be combined together using
logical operators (AND & OR). Maximum nested expression depth allowed
is 5.
For example: display_name = "test" AND metadata.field1.bool_value = true.
Returns
Type
Description
string
setFilter
Filter specifying the boolean condition for the Artifacts to satisfy in
order to be part of the Lineage Subgraph.
The syntax to define filter query is based on https://google.aip.dev/160.
The supported set of filters include the following:
Attribute filtering:
For example: display_name = "test"
Supported fields include: name, display_name, uri, state,
schema_title, create_time, and update_time.
Time fields, such as create_time and update_time, require values
specified in RFC-3339 format.
For example: create_time = "2020-11-19T11:30:00-04:00"
Metadata field:
To filter on metadata fields use traversal operation as follows:
metadata.<field_name>.<type_value>.
For example: metadata.field_1.number_value = 10.0
In case the field name contains special characters (such as colon), one
can embed it inside double quote.
For example: metadata."field:1".number_value = 10.0
Each of the above supported filter types can be combined together using
logical operators (AND & OR). Maximum nested expression depth allowed
is 5.
For example: display_name = "test" AND metadata.field1.bool_value = true.
Parameter
Name
Description
var
string
Returns
Type
Description
$this
static::build
Parameter
Name
Description
artifact
string
Required. The resource name of the Artifact whose Lineage needs to be
retrieved as a LineageSubgraph. Format:
projects/{project}/locations/{location}/metadataStores/{metadatastore}/artifacts/{artifact}
The request may error with FAILED_PRECONDITION if the number of Artifacts,
the number of Executions, or the number of Events that would be returned
for the Context exceeds 1000. Please see
MetadataServiceClient::artifactName() for help formatting this field.
[[["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 Ai Platform V1 Client - Class QueryArtifactLineageSubgraphRequest (1.35.0)\n\nVersion latestkeyboard_arrow_down\n\n- [1.35.0 (latest)](/php/docs/reference/cloud-ai-platform/latest/V1.QueryArtifactLineageSubgraphRequest)\n- [1.34.0](/php/docs/reference/cloud-ai-platform/1.34.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.33.0](/php/docs/reference/cloud-ai-platform/1.33.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.32.1](/php/docs/reference/cloud-ai-platform/1.32.1/V1.QueryArtifactLineageSubgraphRequest)\n- [1.31.0](/php/docs/reference/cloud-ai-platform/1.31.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.30.0](/php/docs/reference/cloud-ai-platform/1.30.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.26.0](/php/docs/reference/cloud-ai-platform/1.26.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.23.0](/php/docs/reference/cloud-ai-platform/1.23.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.22.0](/php/docs/reference/cloud-ai-platform/1.22.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.21.0](/php/docs/reference/cloud-ai-platform/1.21.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.20.0](/php/docs/reference/cloud-ai-platform/1.20.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.19.0](/php/docs/reference/cloud-ai-platform/1.19.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.18.0](/php/docs/reference/cloud-ai-platform/1.18.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.17.0](/php/docs/reference/cloud-ai-platform/1.17.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.16.0](/php/docs/reference/cloud-ai-platform/1.16.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.15.0](/php/docs/reference/cloud-ai-platform/1.15.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.14.0](/php/docs/reference/cloud-ai-platform/1.14.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.13.1](/php/docs/reference/cloud-ai-platform/1.13.1/V1.QueryArtifactLineageSubgraphRequest)\n- [1.12.0](/php/docs/reference/cloud-ai-platform/1.12.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.11.0](/php/docs/reference/cloud-ai-platform/1.11.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.10.0](/php/docs/reference/cloud-ai-platform/1.10.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.9.0](/php/docs/reference/cloud-ai-platform/1.9.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.8.0](/php/docs/reference/cloud-ai-platform/1.8.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.7.0](/php/docs/reference/cloud-ai-platform/1.7.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.6.0](/php/docs/reference/cloud-ai-platform/1.6.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.5.0](/php/docs/reference/cloud-ai-platform/1.5.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.4.0](/php/docs/reference/cloud-ai-platform/1.4.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.3.0](/php/docs/reference/cloud-ai-platform/1.3.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.2.0](/php/docs/reference/cloud-ai-platform/1.2.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.1.0](/php/docs/reference/cloud-ai-platform/1.1.0/V1.QueryArtifactLineageSubgraphRequest)\n- [1.0.0](/php/docs/reference/cloud-ai-platform/1.0.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.39.0](/php/docs/reference/cloud-ai-platform/0.39.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.38.0](/php/docs/reference/cloud-ai-platform/0.38.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.37.1](/php/docs/reference/cloud-ai-platform/0.37.1/V1.QueryArtifactLineageSubgraphRequest)\n- [0.32.0](/php/docs/reference/cloud-ai-platform/0.32.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.31.0](/php/docs/reference/cloud-ai-platform/0.31.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.30.0](/php/docs/reference/cloud-ai-platform/0.30.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.29.0](/php/docs/reference/cloud-ai-platform/0.29.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.28.0](/php/docs/reference/cloud-ai-platform/0.28.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.27.0](/php/docs/reference/cloud-ai-platform/0.27.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.26.2](/php/docs/reference/cloud-ai-platform/0.26.2/V1.QueryArtifactLineageSubgraphRequest)\n- [0.25.0](/php/docs/reference/cloud-ai-platform/0.25.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.24.0](/php/docs/reference/cloud-ai-platform/0.24.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.23.0](/php/docs/reference/cloud-ai-platform/0.23.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.22.0](/php/docs/reference/cloud-ai-platform/0.22.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.21.0](/php/docs/reference/cloud-ai-platform/0.21.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.20.0](/php/docs/reference/cloud-ai-platform/0.20.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.19.0](/php/docs/reference/cloud-ai-platform/0.19.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.18.0](/php/docs/reference/cloud-ai-platform/0.18.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.17.0](/php/docs/reference/cloud-ai-platform/0.17.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.16.0](/php/docs/reference/cloud-ai-platform/0.16.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.15.0](/php/docs/reference/cloud-ai-platform/0.15.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.13.0](/php/docs/reference/cloud-ai-platform/0.13.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.12.0](/php/docs/reference/cloud-ai-platform/0.12.0/V1.QueryArtifactLineageSubgraphRequest)\n- [0.11.1](/php/docs/reference/cloud-ai-platform/0.11.1/V1.QueryArtifactLineageSubgraphRequest)\n- [0.10.0](/php/docs/reference/cloud-ai-platform/0.10.0/V1.QueryArtifactLineageSubgraphRequest) \nReference documentation and code samples for the Google Cloud Ai Platform V1 Client class QueryArtifactLineageSubgraphRequest.\n\nRequest message for\n[MetadataService.QueryArtifactLineageSubgraph](/php/docs/reference/cloud-ai-platform/latest/V1.Client.MetadataServiceClient#_Google_Cloud_AIPlatform_V1_Client_MetadataServiceClient__queryArtifactLineageSubgraph__).\n\nGenerated from protobuf message `google.cloud.aiplatform.v1.QueryArtifactLineageSubgraphRequest`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ AIPlatform \\\\ V1\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getArtifact\n\nRequired. The resource name of the Artifact whose Lineage needs to be\nretrieved as a LineageSubgraph. Format:\n`projects/{project}/locations/{location}/metadataStores/{metadatastore}/artifacts/{artifact}`\nThe request may error with FAILED_PRECONDITION if the number of Artifacts,\nthe number of Executions, or the number of Events that would be returned\nfor the Context exceeds 1000.\n\n### setArtifact\n\nRequired. The resource name of the Artifact whose Lineage needs to be\nretrieved as a LineageSubgraph. Format:\n`projects/{project}/locations/{location}/metadataStores/{metadatastore}/artifacts/{artifact}`\nThe request may error with FAILED_PRECONDITION if the number of Artifacts,\nthe number of Executions, or the number of Events that would be returned\nfor the Context exceeds 1000.\n\n### getMaxHops\n\nSpecifies the size of the lineage graph in terms of number of hops from the\nspecified artifact.\n\nNegative Value: INVALID_ARGUMENT error is returned\n0: Only input artifact is returned.\nNo value: Transitive closure is performed to return the complete graph.\n\n### setMaxHops\n\nSpecifies the size of the lineage graph in terms of number of hops from the\nspecified artifact.\n\nNegative Value: INVALID_ARGUMENT error is returned\n0: Only input artifact is returned.\nNo value: Transitive closure is performed to return the complete graph.\n\n### getFilter\n\nFilter specifying the boolean condition for the Artifacts to satisfy in\norder to be part of the Lineage Subgraph.\n\nThe syntax to define filter query is based on \u003chttps://google.aip.dev/160\u003e.\nThe supported set of filters include the following:\n\n- **Attribute filtering** : For example: `display_name = \"test\"` Supported fields include: `name`, `display_name`, `uri`, `state`, `schema_title`, `create_time`, and `update_time`. Time fields, such as `create_time` and `update_time`, require values specified in RFC-3339 format. For example: `create_time = \"2020-11-19T11:30:00-04:00\"`\n- **Metadata field** : To filter on metadata fields use traversal operation as follows: `metadata.\u003cfield_name\u003e.\u003ctype_value\u003e`. For example: `metadata.field_1.number_value = 10.0` In case the field name contains special characters (such as colon), one can embed it inside double quote. For example: `metadata.\"field:1\".number_value = 10.0` Each of the above supported filter types can be combined together using logical operators (`AND` \\& `OR`). Maximum nested expression depth allowed is 5. For example: `display_name = \"test\" AND metadata.field1.bool_value = true`.\n\n### setFilter\n\nFilter specifying the boolean condition for the Artifacts to satisfy in\norder to be part of the Lineage Subgraph.\n\nThe syntax to define filter query is based on \u003chttps://google.aip.dev/160\u003e.\nThe supported set of filters include the following:\n\n- **Attribute filtering** : For example: `display_name = \"test\"` Supported fields include: `name`, `display_name`, `uri`, `state`, `schema_title`, `create_time`, and `update_time`. Time fields, such as `create_time` and `update_time`, require values specified in RFC-3339 format. For example: `create_time = \"2020-11-19T11:30:00-04:00\"`\n- **Metadata field** : To filter on metadata fields use traversal operation as follows: `metadata.\u003cfield_name\u003e.\u003ctype_value\u003e`. For example: `metadata.field_1.number_value = 10.0` In case the field name contains special characters (such as colon), one can embed it inside double quote. For example: `metadata.\"field:1\".number_value = 10.0` Each of the above supported filter types can be combined together using logical operators (`AND` \\& `OR`). Maximum nested expression depth allowed is 5. For example: `display_name = \"test\" AND metadata.field1.bool_value = true`.\n\n### static::build"]]