Support Questions
Find answers, ask questions, and share your expertise

Does Impala JDBC driver fire DESCRIBE table queries internally for each SELECT query fired via JDBC on Kudu table ?

New Contributor



We have some Kudu tables that are accessed via an API using Impala JDBC. We are observing that a lot of DESCRIBE table statements are fired from the API user even though the API does not call any of the DESCRIBE statements. Is it possible that when the API fires a SELECT query on a Kudu table using Impala JDBC, Impala itself is calling the DESCRIBE statements? Also, is there a way to suppress the DESCRIBE calls and directly execute SELECT?





Cloudera Employee

It's very common for BI/SQL tools to fire off lots of describe statements so they know what do with the data that comes back and for autocomplete.  Are you using JDBC with your own code or another tool?