Adalennis opened a new issue, #9003:
URL: https://github.com/apache/hop/issues/9003
### Apache Hop version?
2.20.0-SNAPSHOT
### Java version?
OpenJDK 21.0.11
### Operating system
macOS
### What happened?
When a pipeline or workflow is run directly, Hop Gui and hop-run give a
declared parameter a different value if the project (or environment) defines a
variable with the same name and no value is given at run time.
Reproduced:
1. Create a workflow that declares parameter `P_2517` with default value
`from-default`, and logs `P_2517=[${P_2517}]` with a Write to log action.
2. In the project, define variable `P_2517=from-project`.
3. Run the workflow from Hop Gui, leaving the Value of `P_2517` empty in Run
Options: the log shows `P_2517=[from-default]`.
4. Run the same workflow with hop-run, without `-p`: `hop-run.sh -j
<project> -r local -f <workflow>.hwf` logs `P_2517=[from-project]`.
A workflow that doesn't declare the parameter logs `from-project` in Hop
Gui, so the project variable is active there.
This code predates #8084, and #8101 didn't change it.
Expected: the same value in both. Either hop-run uses the default, as Hop
Gui and the child-execution rules of #8101 do, or this behaviour is intended
for top-level runs and Hop Gui should do the same. The current behaviour is
documented as it is in #9002 (Working with parameters).
### Issue Priority
Priority: 3
### Issue Component
Component: Hop Gui
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
