You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hop.apache.org by "dave-csc (via GitHub)" <gi...@apache.org> on 2025/07/28 13:11:00 UTC
[I] [Bug]: Value mapper - unexpected/undocumented behaviour (hop)
dave-csc opened a new issue, #5586:
URL: https://github.com/apache/hop/issues/5586
### Apache Hop version?
2.14
### Java version?
17.0.2
### Operating system
Linux
### What happened?
Define a **Value mapper** with no output field (i.e. mapped value will replace the input) and no default value if there is no match.
In this case, the non-matching input isn't changed at all in output: is this the expected behaviour, or should it be forced to NULL?
_Note: when the output field is defined instead, non-matching input is mapped to NULL_
### Issue Priority
Priority: 3
### Issue Component
Component: Transforms, Component: Documentation
--
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] [Bug]: Value mapper - unexpected/undocumented behaviour (hop)
Posted by "hansva (via GitHub)" <gi...@apache.org>.
hansva commented on issue #5586:
URL: https://github.com/apache/hop/issues/5586#issuecomment-4260759886
Interesting, I would expect it to act the same as with an output field specified.
--
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] [Bug]: Value mapper - unexpected/undocumented behaviour (hop)
Posted by "hansva (via GitHub)" <gi...@apache.org>.
hansva closed issue #5586: [Bug]: Value mapper - unexpected/undocumented behaviour
URL: https://github.com/apache/hop/issues/5586
--
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] [Bug]: Value mapper - unexpected/undocumented behaviour (hop)
Posted by "hansva (via GitHub)" <gi...@apache.org>.
hansva commented on issue #5586:
URL: https://github.com/apache/hop/issues/5586#issuecomment-4260760386
.take-issue
--
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] [Bug]: Value mapper - unexpected/undocumented behaviour (hop)
Posted by "hansva (via GitHub)" <gi...@apache.org>.
hansva commented on issue #5586:
URL: https://github.com/apache/hop/issues/5586#issuecomment-4260820213
- I am going to align the behaviour, it should make the value null in both cases (with or without new field)
- Adding an extra option to "keep source value" this way if mapping does not match we will keep the existing value and/or copy the existing value to the destination field
I think this way all use cases would be covered, where you would use the mapper to just fix some invalid values but keep the rest original
--
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