You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hop.apache.org by "mattcasters (via GitHub)" <gi...@apache.org> on 2026/02/13 08:37:06 UTC

[I] [Feature Request]: Make input and output optional in a mapping (hop)

mattcasters opened a new issue, #6570:
URL: https://github.com/apache/hop/issues/6570

   ### What would you like to happen?
   
   Right now, the Simple Mapping transform looks for a "Mapping Input" transform (in the sub-pipeline) to see where it can send input to.  Likewise, the same happens with the "Mapping Output" transform.
   However, in some cases you just have output (you want to read from the same source multiple times in multiple pipelines) and in other cases you have multiple inputs that all write to the same target (without the need for output).
   
   For these scenarios you'd need options in the "Input" and "Output" tabs of the "Simple Mapping" transform that say
   
   [x] There is no input for this mapping.
   [x] There is no output for this mapping. 
   
   ### Issue Priority
   
   Priority: 3
   
   ### Issue Component
   
   Component: Transforms


-- 
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: issues-unsubscribe@hop.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Feature Request]: Make input and output optional in a mapping (hop)

Posted by "CarlosJuncher03 (via GitHub)" <gi...@apache.org>.
CarlosJuncher03 commented on issue #6570:
URL: https://github.com/apache/hop/issues/6570#issuecomment-4086685097

   One idea would be to be able to specify a default value for an input without having to map it directly in the input mapping. Sometimes, we map an input due to one pipeline and don't use it in another, which forces us to use a constant to set it to null. The idea would be to be able to define this directly in the input mapping or even in the input itself (as if it were a function parameter that has a default value when it is not called).


-- 
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: issues-unsubscribe@hop.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Feature Request]: Make input and output optional in a mapping (hop)

Posted by "bamaer (via GitHub) via issues" <is...@hop.apache.org>.
bamaer closed issue #6570: [Feature Request]: Make input and output optional in a mapping
URL: https://github.com/apache/hop/issues/6570


-- 
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: issues-unsubscribe@hop.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Feature Request]: Make input and output optional in a mapping (hop)

Posted by "CarlosJuncher03 (via GitHub)" <gi...@apache.org>.
CarlosJuncher03 commented on issue #6570:
URL: https://github.com/apache/hop/issues/6570#issuecomment-4086694146

   These days, I use mapping a lot in our projects. It's a great basis for logic reuse, but sometimes we run into situations that require us to add one or two transformations to make it work.


-- 
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: issues-unsubscribe@hop.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Feature Request]: Make input and output optional in a mapping (hop)

Posted by "CarlosJuncher03 (via GitHub)" <gi...@apache.org>.
CarlosJuncher03 commented on issue #6570:
URL: https://github.com/apache/hop/issues/6570#issuecomment-4085294993

   One question, is there a way to adjust the input mapping so that if I don't map it in the input mapping, it applies a default value or a null value? This would help a lot, because sometimes I'm forced to put an input in the input mapping because of one pipeline, and in another I don't use that input, and it doesn't allow it, you understand?


-- 
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: issues-unsubscribe@hop.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Feature Request]: Make input and output optional in a mapping (hop)

Posted by "mattcasters (via GitHub)" <gi...@apache.org>.
mattcasters commented on issue #6570:
URL: https://github.com/apache/hop/issues/6570#issuecomment-4085808630

   Hi @CarlosJuncher03 ! 
   So,, it seems like you want to avoid sending a single row with default values to the Mapping pipeline by having the ability to set default values on the input fields on the "Input" tab.  These defaults then become active when `[x] there is no input for this mapping`?  


-- 
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: issues-unsubscribe@hop.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org