@gaurang would you be open to sharing your CREATE TABLEs, CREATE VIEW and the query that has slow planning time? No need for the data, just that should be sufficient for us to understand better what's going on.   Like Lars said, you are probably hitting IMPALA-4242 which explains the slow equivalence class computation, but I'd also like to understand the slow single-node planning time.   Thanks! ... View more

Sure thing, I'm glad you found the culprit. 🙂 ... View more

Thank you.   I will check with team to set the timeout.   Gatsby ... View more

Yes, I thought partitioning on the pattern of filename. For one type of data I have, it is acceptable since there are only 10-15 different types of file name. However; in another type of data, there is a unique "id" field on filename and this field's frequency is very high. So, there would be the threat of creation of lots of partitions which could be compelling for the catalog server. ... View more

Its working now, thanks. ... View more

There's no direct way to find out from the profile unfortunately. If you have a live system you can look at the /threadz page on the impala debug web page (port 25000 on each Impala daemon by default) to see how many hdfs-scan-node threads are running. ... View more

Thank you very much, Tim and Ivan.   I have tested on customer system and with "set disable_codegen=1;" the query does NOT crash the whole impala cluster anymore.   I will inform the customer and provide  him with a link to this discussion ... View more

Hi Jaro, no, the JDBC and ODBC drivers are not open source projects. Best wishes, Lars ... View more