You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dremio database schema is never syncing, when I go to table metadata is not showing columns from the schema
On a new metabase installation I can connect to dremio and see the database but never syncs the schema, fields etc.
I tried on another metabase running version 0.51.3 connected to dremio and with the schema synced, I upgarded to newst version of metabase and when I tried to resync the schema I get the same errror as the new metabase installation.
Metabase version 0.52.8
Dremio version 25.0.0
metabase-dremio-driver version 1.5.0
this is the error I am getting.
2025-01-30T14:30:21.222317+00:00 bi metabase[162556]: original_message: "Lexical error at line 1, column 777. Encountered: "" (126), after : "!""
2025-01-30T14:30:21.222334+00:00 bi metabase[162556]: context: "startLine 1"
2025-01-30T14:30:21.222352+00:00 bi metabase[162556]: context: "startColumn 777"
2025-01-30T14:30:21.222368+00:00 bi metabase[162556]: context: "endLine 1"
2025-01-30T14:30:21.222392+00:00 bi metabase[162556]: context: "endColumn 777"
2025-01-30T14:30:21.222415+00:00 bi metabase[162556]: context: "SQL Query SELECT "fk_ns"."nspname" AS "fk-table-schema", "fk_table"."relname" AS "fk-table-name", "fk_column"."attname" AS "fk-column-name", "pk_ns"."nspname" AS "pk-table-schema", "pk_table"."relname" AS "pk-table-name", "pk_column"."attname" AS "pk-column-name" FROM "pg_constraint" AS "c" INNER JOIN "pg_class" AS "fk_table" ON "c"."conrelid" = "fk_table"."oid" INNER JOIN "pg_namespace" AS "fk_ns" ON "c"."connamespace" = "fk_ns"."oid" INNER JOIN "pg_attribute" AS "fk_column" ON "c"."conrelid" = "fk_column"."attrelid" INNER JOIN "pg_class" AS "pk_table" ON "c"."confrelid" = "pk_table"."oid" INNER JOIN "pg_namespace" AS "pk_ns" ON "pk_table"."relnamespace" = "pk_ns"."oid" INNER JOIN "pg_attribute" AS "pk_column" ON "c"."confrelid" = "pk_column"."attrelid" WHERE fk_ns.nspname ! '^information_schema|catalog_history|pg_' AND ("c"."contype" = 'f'::char) AND ("fk_column"."attnum" = ANY(c.conkey)) AND ("pk_column"."attnum" = ANY(c.confkey)) AND ("fk_ns"."nspname" IN (?, ?, ?)) ORDER BY "fk-table-schema" ASC, "fk-table-name" ASC"
2025-01-30T14:30:21.222479+00:00 bi metabase[162556]: #011at com.dremio.jdbc.impl.DremioJdbc41Factory.newServerPreparedStatement(DremioJdbc41Factory.java:147)
2025-01-30T14:30:21.222498+00:00 bi metabase[162556]: #011at com.dremio.jdbc.impl.DremioJdbc41Factory.newPreparedStatement(DremioJdbc41Factory.java:108)
2025-01-30T14:30:21.222514+00:00 bi metabase[162556]: #011at com.dremio.jdbc.impl.DremioJdbc41Factory.newPreparedStatement(DremioJdbc41Factory.java:50)
2025-01-30T14:30:21.222530+00:00 bi metabase[162556]: #011at cdjd.org.apache.calcite.avatica.AvaticaConnection.prepareStatement(AvaticaConnection.java:358)
2025-01-30T14:30:21.222545+00:00 bi metabase[162556]: #011at com.dremio.jdbc.impl.DremioConnectionImpl.prepareStatement(DremioConnectionImpl.java:299)
2025-01-30T14:30:21.222568+00:00 bi metabase[162556]: #011at com.mchange.v2.c3p0.impl.NewProxyConnection.prepareStatement(NewProxyConnection.java:677)
2025-01-30T14:30:21.222587+00:00 bi metabase[162556]: #011at metabase.driver.sql_jdbc.execute$fn__87660.invokeStatic(execute.clj:479)
2025-01-30T14:30:21.222603+00:00 bi metabase[162556]: #011at metabase.driver.sql_jdbc.execute$fn__87660.invoke(execute.clj:477)
2025-01-30T14:30:21.222618+00:00 bi metabase[162556]: #011at clojure.lang.MultiFn.invoke(MultiFn.java:244)
2025-01-30T14:30:21.222634+00:00 bi metabase[162556]: #011at metabase.driver.sql_jdbc.execute$prepared_statement_STAR_$fn__87729.invoke(execute.clj:539)
Thank you.
The text was updated successfully, but these errors were encountered:
The dremio database schema is never syncing, when I go to table metadata is not showing columns from the schema
On a new metabase installation I can connect to dremio and see the database but never syncs the schema, fields etc.
I tried on another metabase running version 0.51.3 connected to dremio and with the schema synced, I upgarded to newst version of metabase and when I tried to resync the schema I get the same errror as the new metabase installation.
Metabase version 0.52.8
Dremio version 25.0.0
metabase-dremio-driver version 1.5.0
this is the error I am getting.
2025-01-30T14:30:21.222317+00:00 bi metabase[162556]: original_message: "Lexical error at line 1, column 777. Encountered: "
" (126), after : "!""'^information_schema|catalog_history|pg_' AND ("c"."contype" = 'f'::char) AND ("fk_column"."attnum" = ANY(c.conkey)) AND ("pk_column"."attnum" = ANY(c.confkey)) AND ("fk_ns"."nspname" IN (?, ?, ?)) ORDER BY "fk-table-schema" ASC, "fk-table-name" ASC"2025-01-30T14:30:21.222334+00:00 bi metabase[162556]: context: "startLine 1"
2025-01-30T14:30:21.222352+00:00 bi metabase[162556]: context: "startColumn 777"
2025-01-30T14:30:21.222368+00:00 bi metabase[162556]: context: "endLine 1"
2025-01-30T14:30:21.222392+00:00 bi metabase[162556]: context: "endColumn 777"
2025-01-30T14:30:21.222415+00:00 bi metabase[162556]: context: "SQL Query SELECT "fk_ns"."nspname" AS "fk-table-schema", "fk_table"."relname" AS "fk-table-name", "fk_column"."attname" AS "fk-column-name", "pk_ns"."nspname" AS "pk-table-schema", "pk_table"."relname" AS "pk-table-name", "pk_column"."attname" AS "pk-column-name" FROM "pg_constraint" AS "c" INNER JOIN "pg_class" AS "fk_table" ON "c"."conrelid" = "fk_table"."oid" INNER JOIN "pg_namespace" AS "fk_ns" ON "c"."connamespace" = "fk_ns"."oid" INNER JOIN "pg_attribute" AS "fk_column" ON "c"."conrelid" = "fk_column"."attrelid" INNER JOIN "pg_class" AS "pk_table" ON "c"."confrelid" = "pk_table"."oid" INNER JOIN "pg_namespace" AS "pk_ns" ON "pk_table"."relnamespace" = "pk_ns"."oid" INNER JOIN "pg_attribute" AS "pk_column" ON "c"."confrelid" = "pk_column"."attrelid" WHERE fk_ns.nspname !
2025-01-30T14:30:21.222479+00:00 bi metabase[162556]: #011at com.dremio.jdbc.impl.DremioJdbc41Factory.newServerPreparedStatement(DremioJdbc41Factory.java:147)
2025-01-30T14:30:21.222498+00:00 bi metabase[162556]: #011at com.dremio.jdbc.impl.DremioJdbc41Factory.newPreparedStatement(DremioJdbc41Factory.java:108)
2025-01-30T14:30:21.222514+00:00 bi metabase[162556]: #011at com.dremio.jdbc.impl.DremioJdbc41Factory.newPreparedStatement(DremioJdbc41Factory.java:50)
2025-01-30T14:30:21.222530+00:00 bi metabase[162556]: #011at cdjd.org.apache.calcite.avatica.AvaticaConnection.prepareStatement(AvaticaConnection.java:358)
2025-01-30T14:30:21.222545+00:00 bi metabase[162556]: #011at com.dremio.jdbc.impl.DremioConnectionImpl.prepareStatement(DremioConnectionImpl.java:299)
2025-01-30T14:30:21.222568+00:00 bi metabase[162556]: #011at com.mchange.v2.c3p0.impl.NewProxyConnection.prepareStatement(NewProxyConnection.java:677)
2025-01-30T14:30:21.222587+00:00 bi metabase[162556]: #011at metabase.driver.sql_jdbc.execute$fn__87660.invokeStatic(execute.clj:479)
2025-01-30T14:30:21.222603+00:00 bi metabase[162556]: #011at metabase.driver.sql_jdbc.execute$fn__87660.invoke(execute.clj:477)
2025-01-30T14:30:21.222618+00:00 bi metabase[162556]: #011at clojure.lang.MultiFn.invoke(MultiFn.java:244)
2025-01-30T14:30:21.222634+00:00 bi metabase[162556]: #011at metabase.driver.sql_jdbc.execute$prepared_statement_STAR_$fn__87729.invoke(execute.clj:539)
Thank you.
The text was updated successfully, but these errors were encountered: