Exception reading Impala metadata
swood Jun 5, 2015 6:48 PMI am connecting via Teiid into Impala 1.3.1 -> CDH5, using a Cloudera driver.
I am getting a failure when I try to get metadata about the tables in the Teiid connection.
2015-06-05 12:55:45,836 ERROR BaseJdbcMetaDataFactoryImpl,http-bio-8080-exec-37:382 - Cannot get database meta info : /datasources/ImpalaVirtual
org.teiid.jdbc.TeiidSQLException: Error trying to obtain metadata information for the tables that match %: TEIID30489 Unable to load metadata for VDB 91747322 1..
at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:103)
at org.teiid.jdbc.DatabaseMetaDataImpl.getTables(DatabaseMetaDataImpl.java:1528)
...
Caused by: org.teiid.jdbc.TeiidSQLException: TEIID30489 Unable to load metadata for VDB 91747322 1.
at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135)
at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71)
at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:667)
at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:63)
at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:515)
at org.teiid.client.util.ResultsFuture.addCompletionListener(ResultsFuture.java:148)
at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:511)
at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:261)
at org.teiid.jdbc.DatabaseMetaDataImpl.getTables(DatabaseMetaDataImpl.java:1503)
... 146 more
Caused by: org.teiid.core.TeiidComponentException: TEIID30489 Unable to load metadata for VDB 91747322 1.
at org.teiid.dqp.internal.process.Request.initMetadata(Request.java:191)
at org.teiid.dqp.internal.process.Request.processRequest(Request.java:433)
at org.teiid.dqp.internal.process.PreparedStatementRequest.processRequest(PreparedStatementRequest.java:289)
at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:609)
at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:315)
at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:254)
at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:295)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:173)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:258)
at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:171)
at com.sun.proxy.$Proxy181.executeRequest(Unknown Source)
at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:634)
at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:509)
... 148 more
Could this be caused by unexpected table formats? The tables in the schema being access from Impala are Parquet format Using the Parquet File Format with Impala Tables
and there may be unexpected column types etc.
Thanks
Sherman