locations
Creates, updates, deletes, gets or lists a locations
resource.
Overview
Name | locations |
Type | Resource |
Id | google.datalineage.locations |
Fields
The following fields are returned by SELECT
queries:
SELECT
not supported for this resource, use SHOW METHODS
to view available operations for the resource.
Methods
The following methods are available for this resource:
Name | Accessible by | Required Params | Optional Params | Description |
---|---|---|---|---|
process_open_lineage_run_event | exec | projectsId , locationsId | requestId | Creates new lineage events together with their parents: process and run. Updates the process and run if they already exist. Mapped from Open Lineage specification: https://github.com/OpenLineage/OpenLineage/blob/main/spec/OpenLineage.json. |
search_links | exec | projectsId , locationsId | Retrieve a list of links connected to a specific asset. Links represent the data flow between source (upstream) and target (downstream) assets in transformation pipelines. Links are stored in the same project as the Lineage Events that create them. You can retrieve links in every project where you have the datalineage.events.get permission. The project provided in the URL is used for Billing and Quota. | |
batch_search_link_processes | exec | projectsId , locationsId | 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 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. |
Parameters
Parameters can be passed in the WHERE
clause of a query. Check the Methods section to see which parameters are required or optional for each operation.
Name | Datatype | Description |
---|---|---|
locationsId | string | |
projectsId | string | |
requestId | string |
Lifecycle Methods
- process_open_lineage_run_event
- search_links
- batch_search_link_processes
Creates new lineage events together with their parents: process and run. Updates the process and run if they already exist. Mapped from Open Lineage specification: https://github.com/OpenLineage/OpenLineage/blob/main/spec/OpenLineage.json.
EXEC google.datalineage.locations.process_open_lineage_run_event
@projectsId='{{ projectsId }}' --required,
@locationsId='{{ locationsId }}' --required,
@requestId='{{ requestId }}';
Retrieve a list of links connected to a specific asset. Links represent the data flow between source (upstream) and target (downstream) assets in transformation pipelines. Links are stored in the same project as the Lineage Events that create them. You can retrieve links in every project where you have the datalineage.events.get
permission. The project provided in the URL is used for Billing and Quota.
EXEC google.datalineage.locations.search_links
@projectsId='{{ projectsId }}' --required,
@locationsId='{{ locationsId }}' --required
@@json=
'{
"source": "{{ source }}",
"target": "{{ target }}",
"pageSize": {{ pageSize }},
"pageToken": "{{ pageToken }}"
}';
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 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.
EXEC google.datalineage.locations.batch_search_link_processes
@projectsId='{{ projectsId }}' --required,
@locationsId='{{ locationsId }}' --required
@@json=
'{
"links": "{{ links }}",
"pageSize": {{ pageSize }},
"pageToken": "{{ pageToken }}"
}';