[D] Simple mapping - how to deal with passing fields correctly? (hop)

["dave-csc (via GitHub)" <gi...@apache.org>]

GitHub user dave-csc created a discussion: Simple mapping - how to deal with passing fields correctly?

Hello,

when creating a pipeline that can be used via **Simple Mapping** you need to define the input and output map for the fields coming from/to the parent pipeline: those fields will be processed as implemented in the mapping pipeline, the other fields will pass through and won't be changed (unless the mapping pipeline includes transforms that can alter metadata, such as **Select values** and **Group by**).

However, problems arise when in the mapping pipeline a field that happens to have the same name of a "passing" field is created (say `passing_field`). In this case, the pipeline actually creates a renamed field (`passing_field_1`), and the subsequent transforms will refer to `passing_field` rather than `passing_field_1`, with no warning and causing unexpected results.

Is there a way those passing fields can be dealt with (provided that not always their names are actually known in advance)?

Thanks for any ideas :)

GitHub link: https://github.com/apache/hop/discussions/5478

----
This is an automatically sent email for users@hop.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@hop.apache.org

Re: [D] Simple mapping - how to deal with passing fields correctly? (hop)

["mattcasters (via GitHub)" <gi...@apache.org>]

GitHub user mattcasters added a comment to the discussion: Simple mapping - how to deal with passing fields correctly?

Yes, pick completely different fields in your mapping.

GitHub link: https://github.com/apache/hop/discussions/5478#discussioncomment-14587790

----
This is an automatically sent email for users@hop.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@hop.apache.org