Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flow parameter based condition is not working #3330

Open
NidhiManek opened this issue Feb 2, 2024 · 0 comments
Open

Flow parameter based condition is not working #3330

NidhiManek opened this issue Feb 2, 2024 · 0 comments

Comments

@NidhiManek
Copy link

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.

  1. 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.

  1. If we use {job_name:parameter_name} then azkaban allows to upload the zip but it is always evaluated false.
    example:

condition: ${DSP-Trigger-Optimizer-Recommendation:iwit_phase_name} == "Alpha-Synergy" || ${DSP-Trigger-Optimizer-Recommendation:iwit_phase_name} == "Alpha-Dedicated"

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant