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.