Method: projects.locations.batchSearchLinkProcesses

• HTTP request
• Path parameters
• Request body
  • JSON representation
• Response body
  • JSON representation
• Authorization scopes
• IAM Permissions
• ProcessLinks
  • JSON representation
• ProcessLinkInfo
  • JSON representation
• Try it!

Retrieve information about LineageProcesses associated with specific links. LineageProcesses are transformation pipelines that result in data flowing from source to target assets. Links between assets represent this operation.

If you have specific link names, you can use this method to verify which LineageProcesses contribute to creating those links. See the locations.searchLinks method for more information on how to retrieve link name.

You can retrieve the LineageProcess information in every project where you have the datalineage.events.get permission. The project provided in the URL is used for Billing and Quota.

HTTP request

POST https://datalineage.googleapis.com/v1/{parent}:batchSearchLinkProcesses

Path parameters

Parameters
parent	string Required. The project and location where you want to search. It takes the form projects/{project}/locations/{location}.

Request body

The request body contains data with the following structure:

JSON representation
{ "links": [ string ], "pageSize": integer, "pageToken": string }

Fields
links[]	string Required. An array of links to check for their associated LineageProcesses. The maximum number of items in this array is 100. If the request contains more than 100 links, it returns the INVALID_ARGUMENT error. Format: projects/{project}/locations/{location}/links/{link}.
pageSize	integer The maximum number of processes to return in a single page of the response. A page may contain fewer results than this value.
pageToken	string The page token received from a previous locations.batchSearchLinkProcesses call. Use it to get the next page. When requesting subsequent pages of a response, remember that all parameters must match the values you provided in the original request.

Response body

Response message for locations.batchSearchLinkProcesses.

If successful, the response body contains data with the following structure:

JSON representation
{ "processLinks": [ { object (ProcessLinks) } ], "nextPageToken": string }

Fields
processLinks[]	object (ProcessLinks) An array of processes associated with the specified links.
nextPageToken	string The token to specify as pageToken in the subsequent call to get the next page. Omitted if there are no more pages in the response.

Authorization scopes

Requires the following OAuth scope:

• https://www.googleapis.com/auth/cloud-platform

For more information, see the Authentication Overview.

IAM Permissions

Requires the following IAM permission on the parent resource:

• datalineage.locations.searchLinks

For more information, see the IAM documentation.

ProcessLinks

Links associated with a specific process.

JSON representation
{ "process": string, "links": [ { object (ProcessLinkInfo) } ] }

Fields
process	string The process name in the format of projects/{project}/locations/{location}/processes/{process}.
links[]	object (ProcessLinkInfo) An array containing link details objects of the links provided in the original request. A single process can result in creating multiple links. If any of the links you provide in the request are created by the same process, they all are included in this array.

ProcessLinkInfo

Link details.

JSON representation
{ "link": string, "startTime": string, "endTime": string }

Fields
link	string The name of the link in the format of projects/{project}/locations/{location}/links/{link}.
startTime	string (Timestamp format) The start of the first event establishing this link-process tuple. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: "2014-10-02T15:01:23Z" and "2014-10-02T15:01:23.045123456Z".
endTime	string (Timestamp format) The end of the last event establishing this link-process tuple. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: "2014-10-02T15:01:23Z" and "2014-10-02T15:01:23.045123456Z".