1 of 1 people found this helpful
Yes it is expected if both are being imported. Our internal handling of Teiid table names is not case sensitive, so it's currently not allowed to have the same table name with differing case in the same schema. We also currently don't have an automatic resolution for this. One approach to resolve this would be to perform the import, but with an exclusion for the customer table - see the import property excludeTables JDBC Translator - Teiid 8.9 (draft) - Project Documentation Editor
Then you could manually use DDL to define one or both of the customer tables - see chaining repositories Metadata Repositories - Teiid 8.9 (draft) - Project Documentation Editor
And finally you could log an enhancement to propose an automatic resolution strategy, such as adding a table name suffix. To support case-sensitive naming internally however is not likely to happen anytime soon.