Reference documentation and code samples for the Vertex AI V1 API class Google::Cloud::AIPlatform::V1::QueryArtifactLineageSubgraphRequest.
Request message for MetadataService.QueryArtifactLineageSubgraph.
Inherits
- Object
Extended By
- Google::Protobuf::MessageExts::ClassMethods
Includes
- Google::Protobuf::MessageExts
Methods
#artifact
def artifact() -> ::String
-
(::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.
#artifact=
def artifact=(value) -> ::String
-
value (::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.
-
(::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.
#filter
def filter() -> ::String
-
(::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
, andupdate_time
. Time fields, such ascreate_time
andupdate_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
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
. - Attribute filtering:
For example:
#filter=
def filter=(value) -> ::String
-
value (::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
, andupdate_time
. Time fields, such ascreate_time
andupdate_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
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
. - Attribute filtering:
For example:
-
(::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
, andupdate_time
. Time fields, such ascreate_time
andupdate_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
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
. - Attribute filtering:
For example:
#max_hops
def max_hops() -> ::Integer
- (::Integer) — 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.
#max_hops=
def max_hops=(value) -> ::Integer
- value (::Integer) — 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.
- (::Integer) — 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.