GitHub user alexmller added a comment to the discussion: Merge Join - Possible Bug
TL;DR: to me, it seems to work My understanding: You've set the *First Transform* and *Second Transform* property, closed the Merge Dialog with OK and saved the pipeline. After some actions like close/open or running the pipeline, these fields are empty in the GUI and not defined in the pipeline-file. What I've tried: - took the attached file, removed the .XML-suffix, set both transform properties in the GUI and saved. Reopened, ran the pipeline and checked in between whether the Merge Join dialog and the .hpl-file still show both fields - created a new file as instructed above, saved, reopened, ran it and performed the same checks Observation: Once I have selected *First transform* and *Second transform*, hit the *OK* button and then saved the pipeline, it writes the metadata to the `.hpl`-file like this: `<transform` ` <name>Merge Join</name>` ` ...` ` <transform1>DataA</transform1>` ` <transform2>DataB</transform2>` ` ...` `</transform>` The GUI displays both field values the way, they are written to the file. To clear the fields, I have to either remove field values manually or delete input hops to the Merge Join transform. What now? I'm afraid, you would need to analyze it in your environment if you want to pin this down. You can check if the transform properties are written to the pipeline file in the first place. By rolling back the java version, you could rule out that it plays a role in this. GitHub link: https://github.com/apache/hop/discussions/5723#discussioncomment-14605025 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
