Uploaded image for project: 'Apache Hop (incubating)'
  1. Apache Hop (incubating)
  2. HOP-2532

Hop Run: variables in environment or project are not applied to top-level parameters

    XMLWordPrintableJSON

    Details

      Description

      When hop-run defines certain variables before the execution of a pipeline or workflow, for example using system, environment or project variables, they are not applied automatically to a parameter with the same name.

      So for example if you set a variable HOSTNAME=localhost in your lifecycle environment configuration file it is defined as a variable.

      If you then have a parameter in your pipeline called HOSTNAME then that parameter is not set to the variable.

      The effect is that the pipeline thinks the parameter is not set and chooses the default value or nothing if there is no default.

      It's quite nasty to figure out why this is not working and counter intuitive.

      The better way to do this would be to simply see if there is a variable defined for the parameters and to simply use that.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                mcasters Matt Casters
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m