optimus
Usage
source:
type: optimus
config:
host: optimus.com:80
| Key |
Value |
Example |
Description |
|
host |
string |
optimus.com:80 |
Optimus' GRPC host |
required |
max_size_in_mb |
int |
45 |
Max megabytes for GRPC client to receive message. Default to 45. |
|
Outputs
| Field |
Sample Value |
resource.urn |
optimus::https://optimus-host.com/project.namespace.job |
resource.name |
job-name |
resource.service |
optimus |
resource.description |
Sample job description |
ownership.owners[0].urn |
john_doe@example.com |
ownership.owners[0].name |
john_doe@example.com |
lineage.upstreams[].urn |
bigquery::project/dataset/table |
lineage.upstreams[].type |
table |
lineage.upstreams[].service |
bigquery |
lineage.downstreams[0].urn |
bigquery::project/dataset/table |
lineage.downstreams[0].type |
table |
lineage.downstreams[0].service |
bigquery |
properties.attributes |
{} |
MaxCompute Support
The Optimus extractor supports MaxCompute as a dependency source. When a job references MaxCompute resources (with the maxcompute:// prefix), the extractor will:
- Parse MaxCompute fully-qualified names in the format
maxcompute://project.schema.table
- Generate URNs using
maxcompute://{project}.{schema}.{table}
- Include MaxCompute resources as upstream or downstream lineage entries with service
maxcompute
You can also specify a project_id in the extractor config to scope lineage extraction to a specific project.
Contributing
Refer to the contribution guidelines for information on contributing to this module.