¶ Description
Défine global parameters.
¶ Parameters
¶ Parameters tab
Parameters:
- Number of columns to skip
- Only set value if global parameter is empty
¶ Description tab
See dedicated page for more information.
¶ Code tab
setGlobalParameters is a scripted action. Embedded code is accessible and customizable through this tab.
¶ Configuration tab
See dedicated page for more information.
¶ About
The setGlobalParameters action is used to define global parameters dynamically based on the contents of an input table. This allows parameters to be declared once and reused across the ETL pipeline, enhancing modularity and reusability.
The action reads values from a single-row input table where each column name becomes the parameter name, and each cell value becomes the corresponding parameter value. This means you can programmatically set parameters like API keys, default paths, flags, filters, or configuration values based on upstream logic or external sources.
This action is particularly useful in pipelines where you need to:
- Dynamically inject environment-specific settings.
- Reuse the same values in multiple downstream components.
- Define configuration variables in a centralized manner.
Only the first row of the input table is considered. All other rows are ignored.
Parameter values are stored globally across the session and will be accessible from other parts of the pipeline where global parameters are referenced.
The setGlobalParameters action allows you to decouple hardcoded values from your transformation logic. Rather than specifying values directly in each action's parameters, you can reference globally set variables, making the pipeline easier to maintain and configure for multiple environments (e.g., dev, test, prod).
This is especially useful in scenarios where:
- Parameter values need to change depending on user input or configuration files.
- You want to reuse common values like directory paths, default thresholds, or user-specific filters across many steps.
- You are developing modular and scalable ETL pipelines that must adapt to changes with minimal manual edits.
This action works best when used early in the pipeline to define parameters for later stages. It helps ensure that all components operate with the correct contextual settings, making pipelines cleaner and more maintainable.
¶ Example
Input Table
| RunID | param1 | param2 | param3 |
|---|---|---|---|
| run_1 | 123 | ON | /data |
With Number of columns to skip = 1, the action will:
- Skip
RunIDcolumn. - Set global parameter
param1 = 123 - Set global parameter
param2 = ON - Set global parameter
param3 = /data
These parameters can now be used in other actions via the syntax ${param1}, ${param2}, etc.
