Strange Behavior When Querying Physical Datasets with Flight

1

I’m querying physical datasets with flight via python, and when I query a physical dataset, dremio creates the following job:

SELECT COUNT(*) FROM INFORMATION_SCHEMA.“TABLES” WHERE TABLE_NAME = ‘{my query text}’

Is this expected behavior? It’s problematic because the actual query will not run until this generated query times out.

Dremio CE 24.0, data is parquet on NAS data source.

2

Confirmed this is an issue with the Dremio dialect for sqlalchemy.