--- title: Browsing Impala Query Execution within the SQL Editor author: admin type: post date: 2017-12-08T00:00:09+00:00 url: /browsing-impala-query-execution-within-the-sql-editor/ sf_thumbnail_type: - none sf_thumbnail_link_type: - link_to_post sf_detail_type: - none sf_page_title: - 1 sf_page_title_style: - standard sf_no_breadcrumbs: - 1 sf_page_title_bg: - none sf_page_title_text_style: - light sf_background_image_size: - cover sf_author_info: - 1 sf_social_sharing: - 1 sf_related_articles: - 1 sf_sidebar_config: - left-sidebar sf_left_sidebar: - Sidebar-2 sf_right_sidebar: - Sidebar-1 sf_caption_position: - caption-right ampforwp-amp-on-off: - default categories: - Browsing - Version 4 ---
Greetings SQL aficionados!
In Hue 4.2, along with ADLS support, we're introducing a new feature that is sure to make query troubleshooting easier: Impala query execution details right inside of the SQL Editor.
There are three ways to access the new browser:
* Best: Click on the query ID after executing a SQL query in the editor. This will open the mini job [browser][1] overlay at the current query. Having the query execution information side by side the SQL editor is especially helpful to understand the performance characteristics of your queries. * Open the mini job browser overlay and navigate to the queries tab. * Open the job browser and navigate to the queries tab. ## Query capabilities {.p1}Display the list of currently running queries on the user's current Impala coordinator and a certain number of completed queries based on your configuration (25 by default).
Display the [explain][2] plan which outlines logical execution steps. You can verify here that the execution will not proceed in an unexpected way (i.e. wrong join type, join order, projection order). This can happen if the statistics for the table are out of date as shown in the image below by the mention of "cardinality: unavailable". You can obtain statistics by running:
COMPUTE STATS
Display the [summary][3] report which shows physical timing and memory information of each operation of the explain plan. You can quickly find bottlenecks in the execution of the query which you can resolve by replacing expensive operations, repartitioning, changing file format or moving data.
The enable_query_browser flag should be on by default. All you need to access the new browser is to make sure Impala is configured inside of Hue.
[impala]
server_host=
server_port=
[jobbrowser]
enable_query_browser=true
As always, if you have any questions, feel free to comment here or on the [hue-user list][8] or [@gethue][9]!
[1]: https://gethue.com/browsers/
[2]: https://www.cloudera.com/documentation/enterprise/5-12-x/topics/impala_explain.html#explain
[3]: https://www.cloudera.com/documentation/enterprise/5-12-x/topics/impala_shell_commands.html#shell_commands
[4]: https://www.cloudera.com/documentation/enterprise/5-12-x/topics/impala_perf_resources.html
[5]: https://www.cloudera.com/documentation/enterprise/5-12-x/topics/impala_perf_hdfs_caching.html#hdfs_caching_ddl
[6]: https://www.cloudera.com/documentation/enterprise/5-12-x/topics/impala_partitioning.html
[7]: https://www.cloudera.com/documentation/enterprise/5-8-x/topics/impala_file_formats.html#file_format_choosing
[8]: http://groups.google.com/a/cloudera.org/group/hue-user
[9]: https://twitter.com/gethue