I am currently working on modifying an ETL graph that is using ApproximativeJoin to generate some data. I ran into issues after running it a couple of times. The error read something like this:
Metadata “OP_USCCHART2” does not equal to metadata “ACCOUNT_FINAL”
OP_USCCHART2 is the master data and ACCOUNT_FINAL is the output metadata.
Are there rules for Metadata compatibility when using ApproxJoins?
At the ApproximativeJoin component is necessary to set the same metadata on the following ports (zero based indexing):
Input port 0 has equal metadata as output port 2
Input port 1 has equal metadata as output port 3
The output ports 2 and 3 are used for master data records without slave matches (port 2), respectively slave data records without master matches (port 3), so it is necessary to set corresponding metadata.
Every edge of a graph carries some data and the metadata describes the data. You have to set the metadata for every edge of your graph.
At the ApproximativeJoin component you have to set the metadata of some ports as I have written above. It means you have to set properly the metadata on the edges for corresponding ports. You have to set the same metadata of the edge going to the input port 0 as the metadata of the edge connected to the output port 2 and same metadata on the input port 1 and output port 3.