Propagating schema changes
Often during development, it is necessary to change schemas by adding, removing, or re-ordering columns. This often is a very onerous task, especially if a schema is used in multiple jobs.
As discussed earlier in this chapter, storing schemas in the metadata enables the schema to be re-used. If a shared schema is changed, then Talend will prompt to find out if the changes should be applied to all jobs.
If the change is performed, then the next time that the job is opened, the component using the schema will normally be highlighted as in error, because the schema no longer matches.
Talend provides mechanisms within the schema dialogues that takes some of the pain away from ensuring that changes are assimilated into all the jobs.
Getting ready
Open the Talend Job jo_cook_ch02_0010_propagateSchema so that the right-hand palette becomes available. Then, from the metadata palette, open the Generic schema sc_cook_0010_genericCustomer.
How to do it…
Add a new field
emailAddress...
