dave-csc commented on issue #4843: URL: https://github.com/apache/hop/issues/4843#issuecomment-2618773790
Hi @nadment, here's a basic pipeline: 1. Add a transform that generates a single row with a static path (using e.g. a **Data grid** or a **Get variables**): name the field `dst_file` 2. Link this transform to a **Get file names**, specify the file selection in order to look for a single file 3. Link the latter transform to a **Process files**, specify Operation = `Move`, Source file = `filename` (generated by Get file names), Target file = `dst_file` (as named above) The Process files transform fails because the field `dst_file` is not found in the input stream: ``` 2025/01/28 12:30:07 - Sposta file.0 - ERROR: Unexpected error 2025/01/28 12:30:07 - Sposta file.0 - ERROR: org.apache.hop.core.exception.HopException: 2025/01/28 12:30:07 - Sposta file.0 - Couldn't find field 'dst_file' in row! 2025/01/28 12:30:07 - Sposta file.0 - 2025/01/28 12:30:07 - Sposta file.0 - at org.apache.hop.pipeline.transforms.processfiles.ProcessFiles.processRow(ProcessFiles.java:87) 2025/01/28 12:30:07 - Sposta file.0 - at org.apache.hop.pipeline.transform.RunThread.run(RunThread.java:54) 2025/01/28 12:30:07 - Sposta file.0 - at java.base/java.lang.Thread.run(Thread.java:833) 2025/01/28 12:30:07 - Sposta file.0 - Finished processing (I=0, O=0, R=1, W=0, U=0, E=1) ``` However, in Hop GUI you can find evidence of it in various forms: - select the **Get file names**, and then **Show output fields**: the `dst_file` field is listed - select the **Process files**, and then **Show input fields**: the `dst_file` field is listed - when configuring the **Process files** transform, `dst_file` is a selectable field This issue is found in the latest Hop snapshot, too. _Note: in this specific scenario, you can successfully move the file by swapping the first two transforms. The error is that there are listed fields in the subsequent transforms that are actually non usable..._ -- 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]
