MySQL plugin fails when tables differ only by case

[liangchenm]

When using the MySQL plugin in Trino, if a schema contains two tables that differ only in case (e.g. TEST and test), querying metadata results in the following error:
attempted merging values TABLE and TABLE

Is there a recommended way to handle case-sensitive table names in MySQL via Trino?

[liangchenm]

In many real-world scenarios, the database configuration and table naming conventions are already established and running in production, which makes it difficult or impossible to change the database setup to accommodate connector behavior.

I’d like to ask whether it’s possible to introduce a configuration option that preserves the original case of table names when collecting metadata from the target database. This could help avoid issues such as merging tables that only differ in case (e.g., TEST and test)