Talend MDM implementations where master data records are stored in a SQL database include a Staging Area in which MDM users can load data that is then asynchronously validated.
This Staging Area is a mirror of the SQL storage area containing the master data records. The only difference is that the staging area database does not include constraints in its schema (such as not null values or foreign key integrity). However, this does not mean that records with invalid foreign keys can be loaded into the Master database if Foreign Key Integrity is enabled.
For each data container (a data container being an instance of a SQL
storage), a second SQL storage also exists which is the Staging Area for the data
container in question. For example, if you have a data container called
Product, this means that a data container called
Product#STAGING also exists.
using SQL components: execute
INSERTstatements on the database, using JDBC or Data Integration components
using MDM components: use the tMDMOuput and tMDMBulkload components and specify that the data container is
Note that the tMDMOutput component does not allow the insertion or update of non-valid data.Talend MDM
For more details on how to trigger this transfer from the Talend MDM Web UI, see Working with records in the Staging Area.