(Preview) Returns lineage for a given entity object.
post
/20260430/aiDataPlatforms/{aiDataPlatformId}/actions/fetchLineage
(Preview) Returns lineage for a given entity object.
Request
Path Parameters
-
aiDataPlatformId(required): string
Minimum Length:
1Maximum Length:500The [OCID](/iaas/Content/General/Concepts/identifiers.htm) of the AI Data Platform (Data Lake) instance.
Query Parameters
-
limit: integer
Minimum Value:
1Maximum Value:1000For list pagination. The maximum number of results per page, or items to return in a paginated "List" call. For important details about how pagination works, see [List Pagination](/iaas/Content/API/Concepts/usingapi.htm#nine).Default Value:100 -
page: string
Maximum Length:
1024For list pagination. The value of the opc-next-page response header from the previous "List" call. For important details about how pagination works, see [List Pagination](/iaas/Content/API/Concepts/usingapi.htm#nine).
Header Parameters
-
if-match: string
Maximum Length:
1000For optimistic concurrency control. In the PUT or DELETE call for a resource, set the `if-match` parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource's current etag value. -
opc-request-id: string
Maximum Length:
255Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID. The only valid characters for request IDs are letters, numbers, underscore, and dash. -
opc-retry-token: string
Maximum Length:
64A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of running that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and removed from the system, then a retry of the original creation request might be rejected.
The information needed to obtain desired lineage.
Root Schema : FetchEntityLineageDetails
Type:
objectThe information needed to obtain desired lineage.
Match All
The information needed to obtain desired lineage.
Show Source
-
object
ObjectLineageRequestDetails
Details needed by a lineage fetch request.
Nested Schema : ObjectLineageRequestDetails
Type:
objectDetails needed by a lineage fetch request.
Show Source
-
anchorNode(required):
string
Root entity node from with the lineage is to be fetched.
-
direction(required):
string
Allowed Values:
[ "UPSTREAM", "BOTH", "DOWNSTREAM" ]Direction of the lineage returned. -
level(required):
string
Allowed Values:
[ "ENTITY", "COLUMN" ]Indicates the level for lineage fetch. It is one of ENTITY/COLUMN -
maxDepth(required):
integer
Maximum depth to traverse in lineage graph. Depth is measured as number of links from anchor node to matching nodes.
-
nodeFilters:
object NodeFilterObject
Filtering parameter that lets users define which entities are included in the results, while still traversing the full lineage.
-
pathFilters:
object PathFilterObject
Filtering parameter that lets the user control how far the lineage is traversed.
-
shouldIncludeEdges:
boolean
Controls if the edges will be returned with vertices.
Nested Schema : NodeFilterObject
Type:
objectFiltering parameter that lets users define which entities are included in the results, while still traversing the full lineage.
Show Source
-
predicates(required):
object NodeFilterPredicates
List of conditions
Nested Schema : PathFilterObject
Type:
objectFiltering parameter that lets the user control how far the lineage is traversed.
Show Source
-
predicates(required):
object PathFilterPredicates
List of conditions
Nested Schema : NodeFilterPredicates
Type:
objectList of conditions
Show Source
-
displayNameContains:
string
Filters nodes whose display name contains the specified value.
-
typeEquals:
string
Filters nodes whose type exactly matches the specified value.
Nested Schema : PathFilterPredicates
Type:
objectList of conditions
Show Source
-
anchorNodeColumnsIn:
array anchorNodeColumnsIn
Includes only lineage paths where the anchor node's column is one of the specified values, and column-level traversal starts only from these anchor columns.
-
parentIdIn:
array parentIdIn
Includes only those lineage paths in which each node's parent ID is present in the specified list.
-
passThroughNode:
object PassThroughNodeFilterPredicate
Includes only lineage paths that pass through the specified intermediate node.
Nested Schema : anchorNodeColumnsIn
Type:
arrayIncludes only lineage paths where the anchor node's column is one of the specified values, and column-level traversal starts only from these anchor columns.
Show Source
Nested Schema : parentIdIn
Type:
arrayIncludes only those lineage paths in which each node's parent ID is present in the specified list.
Show Source
Nested Schema : PassThroughNodeFilterPredicate
Type:
objectIncludes only lineage paths that pass through the specified intermediate node.
Show Source
-
depth:
integer
Depth of the pass through node from anchor node.
-
id:
string
ID of the pass through node.
Response
Supported Media Types
- application/json
200 Response
Retrieves the Lineage for the entity.
Headers
-
opc-next-page: string
For pagination of a list of items. When paging through a list, if this header appears in the response, then a partial list might have been returned. Include this value as the `page` parameter for the subsequent GET request to get the next batch of items.
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : EntityLineage
Type:
objectLineage for a data entity.
Match All
Lineage for a data entity.
Show Source
-
object
ObjectLineage
Lineage for an object.
Nested Schema : ObjectLineage
Type:
objectLineage for an object.
Show Source
-
links(required):
array links
Maximum Number of Items:
1000Set of links between the objects in the 'objects' set. -
nodes(required):
array nodes
Maximum Number of Items:
1000Set of links that are involved in the lineage.
Nested Schema : links
Type:
arrayMaximum Number of Items:
1000Set of links between the objects in the 'objects' set.
Show Source
-
Array of:
object LineageRelationship
Declares how two elements of object lineage are related.
Nested Schema : nodes
Type:
arrayMaximum Number of Items:
1000Set of links that are involved in the lineage.
Show Source
-
Array of:
object LineageObject
Object describing an individual element of object lineage.
Nested Schema : LineageRelationship
Type:
objectDeclares how two elements of object lineage are related.
Show Source
-
fromNodeId:
string
Minimum Length:
1Maximum Length:255Object key of source lineage element. -
properties:
object properties
Maximum Number of Properties:
100Additional Properties Allowed: additionalPropertiesA map of maps that contains the properties which are specific to the entity type. Each entity type definition defines it's set of required and optional properties. The map keys are category names and the values are maps of property name to property value. Every property is contained inside of a category. Most data entities have required properties within the "default" category. Example: `{"properties": { "default": { "key1": "value1"}}}` -
providerType:
string
Minimum Length:
1Maximum Length:255Type of the relationship. -
toNodeId:
string
Minimum Length:
1Maximum Length:255Object key of target lineage element. -
type:
string
Minimum Length:
1Maximum Length:255Type of the relationship.
Nested Schema : properties
Type:
objectMaximum Number of Properties:
100Additional Properties Allowed
Show Source
-
object additionalProperties
Additional Properties Allowed: additionalPropertiesKey-value pair representing properties of a data entity scoped to a category. Example: `{"key1": "value1"}`
A map of maps that contains the properties which are specific to the entity type. Each entity type
definition defines it's set of required and optional properties. The map keys are category names and the
values are maps of property name to property value. Every property is contained inside of a category. Most
data entities have required properties within the "default" category.
Example: `{"properties": { "default": { "key1": "value1"}}}`
Nested Schema : additionalProperties
Type:
objectAdditional Properties Allowed
Show Source
-
string
The string value of the data asset property.
Key-value pair representing properties of a data entity scoped to a category.
Example: `{"key1": "value1"}`
Nested Schema : LineageObject
Type:
objectObject describing an individual element of object lineage.
Show Source
-
depth:
integer
Depth is measured as number of links from anchor node to matching nodes.
-
direction:
string
Allowed Values:
[ "UPSTREAM", "BOTH", "DOWNSTREAM" ]Direction of the lineage. -
displayName:
string
Minimum Length:
1Maximum Length:255Display name of the object. -
id:
string
Minimum Length:
1Maximum Length:255Key of the object, such as an entity, about which this lineage applies. -
parentId:
string
Minimum Length:
1Maximum Length:255Key of the parent object for this object. -
properties:
object properties
Maximum Number of Properties:
100Additional Properties Allowed: additionalPropertiesA map of maps that contains the properties which are specific to the entity type. Each entity type definition defines it's set of required and optional properties. The map keys are category names and the values are maps of property name to property value. Every property is contained inside of a category. Most data entities have required properties within the "default" category. Example: `{"properties": { "default": { "key1": "value1"}}}` -
qualifiedName:
string
Minimum Length:
1Maximum Length:255External source identifier name of the object. -
type:
string
Minimum Length:
1Maximum Length:255Type name of the object.
Nested Schema : properties
Type:
objectMaximum Number of Properties:
100Additional Properties Allowed
Show Source
-
object additionalProperties
Additional Properties Allowed: additionalPropertiesKey-value pair representing properties of a data entity scoped to a category. Example: `{"key1": "value1"}`
A map of maps that contains the properties which are specific to the entity type. Each entity type
definition defines it's set of required and optional properties. The map keys are category names and the
values are maps of property name to property value. Every property is contained inside of a category. Most
data entities have required properties within the "default" category.
Example: `{"properties": { "default": { "key1": "value1"}}}`
Nested Schema : additionalProperties
Type:
objectAdditional Properties Allowed
Show Source
-
string
The string value of the data asset property.
Key-value pair representing properties of a data entity scoped to a category.
Example: `{"key1": "value1"}`
400 Response
Bad Request (invalid query parameters, malformed headers, and so on).
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
401 Response
Unauthorized (missing or expired credentials, and so on).
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
404 Response
Not Found. The requested resource was not found.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
409 Response
Conflict. Request conflicts with the current state of the resource.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
412 Response
Precondition Failed (One or more conditions in request failed).
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
429 Response
Too Many Requests. Too many requests sent to the server in a short period.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
500 Response
Internal Server Error. The server encountered an unexpected condition preventing fulfilment of the request.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
Default Response
Unknown Error. Error is not recognized by the system.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.