[BUG] Using Power BI with aliased indices

What is the bug?
We have been trying to connect Power BI to our OpenSearch domains but are having troubles with using aliased indexes.

This looks to be down to SHOW tables LIKE %; reporting an instance of the alias for every index that is using it. This in itself is handled by Power BI, but then when you try to connect to the aliased index/table Power BI reports an error 'Expression.Error: The key matched more than one row in the table.'

Can you offer any guidance?

How can one reproduce the bug?
Steps to reproduce the behavior:

1. Make a new OpenSearch data source:
   

Select one of the instances of the aliased index

3. See error

What is the expected behavior?
Ideally the aliased index should only show up once in the list of indices, but even if it does selecting it should continue and not show an error.

What is your host/environment?

• OS: Windows 10
• Version: OpenSearch 1.3, but same behavior on OpenSearch 2.7
  Driver version: signed_opensearch-sql-odbc-win64-1.1.0.1.msi
• Plugins: Nothing added just the standard AWS managed OpenSearch

Start by reproducing the SHOW tables LIKE % result with aliased indices, then follow the OpenSearch ODBC catalog behavior used by Power BI when selecting an aliased table. Done means each alias appears once and selecting it no longer produces the “key matched more than one row” error.