MongoDB import name conflict issues ----------------------------------- Key: TEIID-5876 URL: https://issues.redhat.com/browse/TEIID-5876 Project: Teiid Issue Type: Bug Components: Misc. Connectors Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Major Fix For: 14.0 Original Estimate: 4 hours Time Spent: 2 hours Remaining Estimate: 2 hours There are two issues with the import logic and naming: 1. There's an assumption that any table in the schema was created by the mongodb import. In general this is not true as other imports or ddl may have already run. 2. If a child construct has a field name that matches an existing table, the two entities will get intertwined in the metadata, which is invalid.