One Star

Propagate schema changes backwards in the job sequence (prev. comp)?

Hi, I am using the repository schema (not built in) for my output
I have made an update to the repository, but the preceding component (in this case a tMap) schema doesn't change accordingly
The "Sync columns" button goes the other way, changing my output to match the schema of the tMap
How can I get the tMap to update to match the changes to the repository connection?
Do I need to delete the connection and create a new one? What if I had put a lot of work into configuring my tMap component behaviour?
Thanks Smiley Happy
2 REPLIES
Four Stars

Re: Propagate schema changes backwards in the job sequence (prev. comp)?

Hi,
tMap carries input schema to its output from earlier components. If you are using different metadata from repository for output component after tMap, I don't think that the input metadata will reverse from tMap to its first input component !!!. If you want different schema from output, you can modify the same in tMap itself or convert output schema to built-in.
But, I think that, you can can't do what you are thinking.
Vaibhav
One Star

Re: Propagate schema changes backwards in the job sequence (prev. comp)?

Thanks for your answer Smiley Happy