Migration: Automatic variables
Most automatic variables are supported in the Data Productivity Cloud.
For more details of variable migration in general, read Migration: Variables.
Migration path
The following table lists the equivalents for some commonly used automatic variables. You will need to manually edit pipeline components to use the correct variables.
| Matillion ETL variable | Data Productivity Cloud variable |
|---|---|
| task_id | .thisComponent.taskId |
| job_name | .thisPipeline.name |
| run_history_id | .rootPipeline.executionId |
| project_id | .project.id |
| version_name | .project.artifact.versionName |
| environment_name | .environment.name |
Not supported
The following Matillion ETL automatic variables don't have equivalents in the Data Productivity cloud.
- detailed_error
- queued_time
- component_id
- job_id
- project_group_id
- project_group_name
- version_id
- environment_endpoint
- environment_port
Not yet supported
The following Matillion ETL automatic variables don't currently have equivalents in the Data Productivity cloud, but support will be added in a future release. See our Roadmap for details.
- Environment properties such as:
- environment_username
- environment_database
- environment_default_schema
Accessing through scripts
The Data Productivity cloud doesn't support directly accessing automatic variables through the Python Script or Bash Script components.
If you require this functionality, you can use an Update Scalar component to write the values to user-defined variables, which can then be passed to the script.
For more alternative options available when migrating Python and Bash scripts, read Migration: Bash and Migration: Python.