Solved! Go to Solution.
Input and Output components have Encoding property in the Basic or Advanced properties. You can just choose UTF-8 instead of ISO-885915 for all components in your Job Designs.
If you need some in an enconding and some other into another, maybe it's probably easier to have two separate subJob, one on UTF-8 the other one on ISO-885915 on the components.
Another way is to call user_routines which have some method to encode the data on the fly into a tMap or other components.
From my point of view it's safe.
Normally, you don't need to cast (for it you mean encode) at all the object.
Once your data is read with the right encoding from the source and become an Object (String, Float, ...) and then is written using the right encoding too; you don't care about the Life of the object during the date flow.
For example you can have a source in ISO-885915 and a target in UTF-16, you just need to indicate the right encoding for each one; but nothing to do in the middle components like tMap, etc...
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Watch the recorded webinar!
Learn how to do cool things with Context Variables
Find out how to migrate from one database to another using the Dynamic schema
Pick up some tips and tricks with Context Variables