This content has been marked as final. Show 3 replies
has an example of how to bring in custom metadata into EDC.
The steps include:
The first two metadata loads ran successfully. However, the last metadata load for the Custom Lineage fails.
Consequently, I don’t see any upstream and downstream details under the Lineage and Impact tab for Map_CDB_to_Policy_Model.
In the log, I see that parsing failed: String index out of range. I see 3 occurrences.
Is there a limit on the length of the "To Object" in the Custom Lineage file?
Since I don't have catalog resources for OracleWB and Prologic_filestore, is this contributing to the errors?
Do I have to have these resources in order to display Custom Lineage?
Is there a model for OracleWB that can be provided for the example?