apache / apache/hop

[Feature Request]: Inside a pipeline that is referenced by "Pipeline executed to capture logging" path variables are displayed incorrectly; plus minor issues

Open
#2,672 0 comments 0 reactions 0 assignees View on GitHub
awaiting triage Documentation Hop Gui P3
Dominant language
Java
Stars
1.5k
Forks
476
Avg merge
18h 33m
Merged PRs (30d)
204

Description

### What would you like to happen?

Migration: https://issues.apache.org/jira/browse/HOP-4094

**Issue I (main issue):**
In a project that uses workflow and pipeline logging, we have a pipeline referenced by "Pipeline executed to capture logging" ("logging_a_pipeline.hpl" in "logging"-subfolder) inside the Metadata object "Pipeline_Log".

The "Pipeline_Log" captures the output of "produce_data.hpl" in "sub"-subfolder.

The pipeline "logging_a_pipeline.hpl" uses two "Text file input" transforms whose paths use variables ("${Internal.Entry.Current.Folder}" or "${Internal.Pipeline.Filename.Directory}", the problem is the same for both).

The tooltip on the paths in the "Text file input" transforms does NOT show the path that is actually produced when the project runs, and is therefore incorrect (or, at least, very misleading).

The exact symptom is that during execution of the project the variables actually hold the path to "sub" folder that contains "produce_data.hpl", but not (as one would expect and what the tooltip shows!) the path to the "logging" folder that contains "logging_a_pipeline.hpl".

How to reproduce:

simply start "main.hwf", and then experiment with the paths in the "Text file input" transforms in "logging_a_pipeline.hpl".

**Issue II (minor):**
The documentation on the checkbox "Logging parent pipelines only" in https://hop.apache.org/manual/latest/metadata-types/pipeline-log.html is missing.

I was quite confused about the semantic, but what I think I could find out is, that in case the checkbox is checked, the log is ONLY produced if the pipeline is started directly. Is that correct?

see

https://hop.apache.org/manual/latest/metadata-types/pipeline-log.html
https://hop.apache.org/manual/latest/metadata-types/workflow-log.html

**Issue III (minor):**
The paths under "Capture output of the following pipelines" can use variables (here: "${PROJECT_HOME}", but are

missing the blue diamond symbol which is normally present
CTRL+SPACE does not work
Issue IV (minor):
The path in "Pipeline executed to capture logging" does not accept CTRL+V

![image](https://user-images.githubusercontent.com/1140235/225934069-0ae8a273-46ea-4d87-89ff-cd675044096a.png)
![image](https://user-images.githubusercontent.com/1140235/225934137-bf5d20e7-5380-4624-85ca-84eeb8a030b6.png)

[path_problem.zip](https://github.com/apache/hop/files/11002382/path_problem.zip)

### Issue Priority

Priority: 3

### Issue Component

Component: Documentation, Component: Hop Gui

Contributor guide

Open the contributing guide

Research direction

Reproduce the behavior by starting main.hwf and inspecting logging_a_pipeline.hpl, produce_data.hpl, and the Pipeline_Log metadata object, especially the Text file input paths. Compare the displayed tooltips with the runtime paths, then review the pipeline-log documentation and the controls for variable assistance and paste support. Done means the reported path, documentation, autocomplete, and paste issues are verified and addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
documentation, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.