Not helpful yet, but promising... PIVOT keyword is reserved for future use! https://www.cloudera.com/documentation/enterprise/6/6.2/topics/impala_reserved_words.html ... View more

Alex,   Thank you again.   Subquery approach has been recommended to our team as a long term solution. However, for short-tem solution to avoid regression impact, using view with limited partitions has been selected.   If I remember correctly, in MySQL `table A` data can be limited by `ON Clause` before joining so that cadidates for join can be reduced.   Thank you for your valuable comment. Gatsby ... View more

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

This blog post provides a nice introduction to Impala's admission control:   https://blog.cloudera.com/blog/2016/12/resource-management-for-apache-impala-incubating/   There are a few ways to inspect a query's memory usage. The query profile and summary will have stats about peak memory usage per host and for each operator in the query. The stats are generally per-host, instead of cluster-wide aggregates. If you're using impala-shell, you can also "set live_summary=1" to get a live update of the query as it makes progress.   If you want to see the live state of all queries running on an Impala daemon as an admin, you can look at the "memz" tab of the Impala web UI (by default on port 25000). That will show the full tree of tracked memory from the process down to the operator level.   Cloudera Manager also has various charts of aggregate memory usage. ... View more