Thx for the input. I'll file a JIRA as it seems to be a bug vs a configuration issue.
In my case it seems to complain about PERFORMANCE_SCHEMA in MySQL not actually the info_schema. --Andries > On Jan 26, 2016, at 9:35 AM, Magnus Pierre <[email protected]> wrote: > > I’ve seen it as well. My unqualified guess is that the engine gets confused > with multiple databases named INFORMATION_SCHEMA and which makes it combine > metadata from two different engines. Gets the metadata of a table from one > and tries to use on the other… > > Regards, > Magnus > >> 26 jan 2016 kl. 17:19 skrev Andries Engelbrecht <[email protected]>: >> >> Anyone run into issues with Drill INFORMATION_SCHEMA queries when using the >> JDBC plugin with MySQL? >> >> In my case some tools are interrogating Drill's Metadata, which then fails >> when enabling the JDBC plugin with MySQL. >> Using Drill 1.4 and MySQL 5.1.73 >> >> {query} >> SELECT DISTINCT TABLE_SCHEMA as NAME_SPACE, TABLE_NAME as TAB_NAME FROM >> INFORMATION_SCHEMA.COLUMNS WHERE TABLE_SCHEMA <>'INFORMATION_SCHEMA' and >> TABLE_SCHEMA <> 'sys'; >> {/query} >> >> {result} >> Error: SYSTEM ERROR: MySQLSyntaxErrorException: Unknown table engine >> 'PERFORMANCE_SCHEMA' >> >> Fragment 0:0 >> {/result} >> >> Thanks >> --Andries >
