CarlosJuncher03 opened a new issue, #6478:
URL: https://github.com/apache/hop/issues/6478
### What would you like to happen?
Many Hop dialog fields support variable substitution (${...}), but they
don’t support computed/conditional values derived from other variables.
Today, when you want to parameterize pipelines by environment or mode (e.g.,
full load vs on-demand), you often need something like:
if ${VAR} = 10, then use 4, otherwise 6
The issue is that this currently requires extra steps (compute the value +
set a variable), which increases complexity and leads to duplicated logic
across pipelines.
The idea is to add support for expressions (including conditional logic)
directly in configurable fields, in addition to simple ${variable} substitution.
Examples
if(${variable} = '10', 4, 6)
if(${mode}='X', 1, 9) (numeric result)
Note / motivation
I noticed this could significantly improve the pipeline authoring
experience, especially in scenarios where the process switches between full
extraction and on-demand runs. For example: if it’s a full load, I’d set X
copies/threads; otherwise, I’d set a different value—without needing extra
branches or helper steps just to achieve that.
We can bring this to the community to see if others find it valuable and
whether it’s feasible to add to Hop. Low-code tools like Appsmith and Lowcoder
already use this approach, and it generally makes parameterization much easier.
### 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]
