@thewayofthinkin - No, the view should get expanded and then the resulting query will access the already loaded metadata of the table. From the order of the queries it looked like the view may be queried first, then the table, which could explain why the former took much longer than the latter. ... View more

Hi gaurang,   Does the long query time only occur the first time you query a view after altering it? In that case if could be related to metadata loading for the underlying table. How many partitions and files do these tables typically have? You could also check the log files for anything suspicious.   Cheers, Lars ... View more

Hi hakki,   You could try partitioning your table and using the "show partitions" command to narrow down the set of files a row might be in. Can you give more context on the usecase without sharing private information?   Cheers, Lars ... View more

Hi maurin,   you should be able to tell from the query profile. Run the query and then immediately after run "profile;" in the Impala shell to display the profile information, which will also contain information about the table scans. Feel free to post the profile here if you need help inspecting it.   Cheers, Lars ... View more

Hi Khalef,   I don't know the answer to your question myself, but I asked around for an expert on Kite and learned that the best source for help would be the Kite project itself. You probably found their website already: http://kitesdk.org/docs/current/   It also links to their mailing list and I would like to ask you to post your question there: https://groups.google.com/a/cloudera.org/forum/#!forum/cdk-dev   Apologies for the inconvenience. Best wishes, Lars ... View more

Hi Khalef,   Have you had a look at this blog post covering Kite? https://blog.cloudera.com/blog/2014/06/how-to-use-kite-sdk-to-easily-store-and-configure-data-in-apache-hadoop/   Cheers, Lars ... View more

Impala should write its logging information to several logfiles, which contain the words INFO, WARNING, ERROR, FATAL in their name. Have you checked all of them for the affected time range? ... View more

This looks more like the affected impalad crashed or somehow disappeared from the cluster. Can you check it's logs to see why it disconnected from the statestored? ... View more

Hi scotty603, does the impalad on the affected node start up and keep running, despite the ThriftServer exception? Have you checked that port 22000 is actually unused prior to starting impala? Cheers, Lars ... View more