You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to define the flow of a dag based on the flow parameter passed to the dag. based on the value given to the flow parameter, we want to take call on whether to run a particular node or not. I have tried different ways but it's not working.
Generally, we access flow parameter in .flow file as {parameter_name}, when using {parameter_name} in the condition, azkaban gives error when uploading the zip.
example:
condition: ${iwit_phase_name} == "P2-P1"
Validator Directory Flow reports errors: Invalid condition for DSP Trigger: cannot resolve the condition. Please check the syntax for supported conditions.
If we use {job_name:parameter_name} then azkaban allows to upload the zip but it is always evaluated false.
example:
The concern is if we can access flow parameter as {parameter_name} in whole flow then why not in condition config. Can we please change the way azkaban parses the condition- always requiring job_name in the condition- as we should be able to access flow parameters without job_name and only JOB_PROP_FILE variables should be requiring job_name.
Thanks!
The text was updated successfully, but these errors were encountered:
We want to define the flow of a dag based on the flow parameter passed to the dag. based on the value given to the flow parameter, we want to take call on whether to run a particular node or not. I have tried different ways but it's not working.
example:
example:
The concern is if we can access flow parameter as {parameter_name} in whole flow then why not in condition config. Can we please change the way azkaban parses the condition- always requiring job_name in the condition- as we should be able to access flow parameters without job_name and only JOB_PROP_FILE variables should be requiring job_name.
Thanks!
The text was updated successfully, but these errors were encountered: