LPETIT458 opened a new issue, #8234:
URL: https://github.com/apache/hop/issues/8234
## Related issue
Follow-up to #7209 (fixed in 2.19 — variable substitution for transform file
paths on remote Hop Server). The general case described in #7209 now works
correctly for us on [VOTRE VERSION], **but the issue reappears specifically
when the "Export linked resources to server" option is enabled on the run
configuration.**
## Apache Hop version?
2.19.0
## Java version?
JDK 21
## Operating system
Red Hat Enterprise Linux
## What happened?
### Scenario
- A pipeline extracts data from a source table (e.g. `dwh.my_table`) and
feeds two file-output transforms, each using variables in the filename field:
- **Hop file output** — Filename: `${NFS}/${REP}/extraction-10000.cube`
- **Text file output** — Filename: `${NFS}/${REP}/mon_fichier-10000`
(extension `txt`)
- `${NFS}` and `${REP}` are defined at the project/environment level.
- The pipeline runs via a Pipeline Run Configuration using:
- Engine type: **Hop remote pipeline engine**
- Hop server: a registered remote Hop Server
- Run Configuration: `local`
- **Export linked resources to server**: checked
### Expected result
The variables `${NFS}` and `${REP}` should resolve to their configured
values, exactly as they do when "Export linked resources to server" is left
unchecked.
### Actual result
The pipeline executes without error ("OK"), but the output files are written
to the **wrong path**. Inspecting the Hop Server's install directory
(`HOP_HOME`) shows a folder **literally named `${DATA_PATH_1}`** created at the
root of the Hop installation folder — i.e. a variable reference is used
verbatim as a literal path segment instead of being substituted, and the
resolved location ends up nested inside the server's own Hop install directory
rather than the intended target path.
With "Export linked resources to server" **unchecked**, the same pipeline
resolves `${NFS}/${REP}/...` correctly.
### Steps to reproduce
1. Define variables (e.g. `${NFS}`, `${REP}`) in the project/environment
configuration.
2. Build a pipeline with a source input feeding two File-type transforms
(reproduced with both a Hop file output `.cube` and a Text file output `.txt`),
each using `${NFS}/${REP}/<filename>` in the Filename field.
3. Create a Pipeline Run Configuration with Engine type "Hop remote pipeline
engine", pointing to a remote Hop Server.
4. Check **"Export linked resources to server"**.
5. Run the pipeline.
6. Observe: execution reports success, but files land under a literal
`${DATA_PATH_1}`-named folder inside the Hop Server's own install directory
instead of the resolved `${NFS}/${REP}` path.
7. Uncheck "Export linked resources to server" and re-run: paths resolve
correctly.
### Additional context
- Systematic — reproduces on every File-type transform tested, not
intermittent.
- Same incorrect resolution occurs when the path points to an **S3
location**, not just local/NFS paths — suggesting the substitution breaks
upstream of the specific VFS/file-transform implementation, in how variables
are resolved for the exported/linked resource before being handed to the
transform.
- Affects both Pipeline and Workflow run configurations.
- A minimal reproduction pipeline is attached (see comments) — extraction
feeding a Hop file output and a Text file output, both using `${NFS}/${REP}` in
their Filename field.
## Issue Priority
Priority: 1 (systematic regression affecting all File-type transforms in a
common remote-execution setup; same severity class as #7209, which was P1)
## Issue Component
Component: Hop Server
## Complement information
Sama problem with S3 output : name for S3 connexion became a name of
directory in path on hop-server....
--
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]
