You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by "Abacn (via GitHub)" <gi...@apache.org> on 2026/02/02 16:51:48 UTC
[I] [Bug]: Beam Yaml Jinja option may conflict with well known Pipeline option [beam]
Abacn opened a new issue, #37475:
URL: https://github.com/apache/beam/issues/37475
### What happened?
Saying I have a Yaml pipeline has a Jinja vairable 'projectId', it may conflicts with the well known pipeline option `project` due to here
https://github.com/apache/beam/blob/112685de58d7b24b70b8d8eb7171f0e28b35a2f1/sdks/python/apache_beam/yaml/main.py#L63
jinja_variable_parser may "unambiguously" parsed "--project" as "--projectId"
This can cause weird error `ValueError: Pipeline has validations errors: Missing required option: project.` when submitting pipeline to Dataflow
We should set `allow_abbrev` to False. But this still doesn't fully avoid confliction when a jinja variable also named `project`
### Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
### Issue Components
- [ ] Component: Python SDK
- [ ] Component: Java SDK
- [ ] Component: Go SDK
- [ ] Component: Typescript SDK
- [ ] Component: IO connector
- [ ] Component: Beam YAML
- [ ] Component: Beam examples
- [ ] Component: Beam playground
- [ ] Component: Beam katas
- [ ] Component: Website
- [ ] Component: Infrastructure
- [ ] Component: Spark Runner
- [ ] Component: Flink Runner
- [ ] Component: Samza Runner
- [ ] Component: Twister2 Runner
- [ ] Component: Hazelcast Jet Runner
- [ ] Component: Google Cloud Dataflow Runner
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: Beam Yaml Jinja option may conflict with well known Pipeline option [beam]
Posted by "derrickaw (via GitHub)" <gi...@apache.org>.
derrickaw closed issue #37475: [Bug]: Beam Yaml Jinja option may conflict with well known Pipeline option
URL: https://github.com/apache/beam/issues/37475
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: Beam Yaml Jinja option may conflict with well known Pipeline option [beam]
Posted by "Abacn (via GitHub)" <gi...@apache.org>.
Abacn closed issue #37475: [Bug]: Beam Yaml Jinja option may conflict with well known Pipeline option
URL: https://github.com/apache/beam/issues/37475
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: Beam Yaml Jinja option may conflict with well known Pipeline option [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #37475:
URL: https://github.com/apache/beam/issues/37475#issuecomment-4882059216
This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: Beam Yaml Jinja option may conflict with well known Pipeline option [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #37475:
URL: https://github.com/apache/beam/issues/37475#issuecomment-5166941620
This issue has been closed due to lack of activity. If you think that is incorrect, you can reopen the issue at any time.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: Beam Yaml Jinja option may conflict with well known Pipeline option [beam]
Posted by "krishiekrashie (via GitHub)" <gi...@apache.org>.
krishiekrashie commented on issue #37475:
URL: https://github.com/apache/beam/issues/37475#issuecomment-3842021909
Hi, can I work on this issue? Please let me contribute
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: Beam Yaml Jinja option may conflict with well known Pipeline option [beam]
Posted by "Abacn (via GitHub)" <gi...@apache.org>.
Abacn commented on issue #37475:
URL: https://github.com/apache/beam/issues/37475#issuecomment-3837207221
Fixed the case of `a_jinja_variablel.startswith(a_pipeline_option)`. Re-open to track the scenario that jinja_variable sharing the same name with pipeline option
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: Beam Yaml Jinja option may conflict with well known Pipeline option [beam]
Posted by "Abacn (via GitHub)" <gi...@apache.org>.
Abacn commented on issue #37475:
URL: https://github.com/apache/beam/issues/37475#issuecomment-3842462496
Hi @krishiekrashie, thanks for your interests. The remaining part is a subtle issue and this bug is left for tracking purpose, to warn that users should not create jinja variable that has same name with well known pipeline options. Let me adjust the priority.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: Beam Yaml Jinja option may conflict with well known Pipeline option [beam]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #37475: [Bug]: Beam Yaml Jinja option may conflict with well known Pipeline option
URL: https://github.com/apache/beam/issues/37475
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org