What's New in Hue
Learn about the new features of Hue in Cloudera Runtime 7.2.16.
Ability to rerun queries from the Job Browser page
A new option called Re Execute has been added to the page. You can select a query you want to rerun and click Re Execute. It takes you to the query editor to enable you to make changes and submit the query. For more information, see Rerunning a query from the Job Browser page.
Hue Query Processor scan frequency decreased to 5 minutes
The Hue Query Processor scans the event processor pipeline to retrieve the Hive query history and query details and displays them on the Job Browser page. The scan frequency has been decreased from 2 milliseconds to 5 minutes to optimize resource utilization. As a result, you may notice a delay in viewing the query history and query details on the Job Browser page for queries that finish executing in less than 5 minutes. However, you can still view the query history from the Query history tab below the query editor. See Configuring the Hue Query Processor scan frequency.
Ability to enable and disable auto-creation of user home directories in S3 and ADLS
If you have enabled fine-grained authorization to access S3 or ADLS, then Hue is configured to automatically create user home directories, by default. When a new user logs into Hue, Hue automatically creates a home directory for that user on S3 or ADLS. You can disable the automatic creation of user home directories by setting the autocreate_user_dir flag to false in the Hue Service Advanced Configuration Snippet. For more information, see Disabling automatic creation of user home directories on S3/ABFS.
Query Processor API to force data cleanup
Hue Query Processor cleans up queries older than a set number of days as per the set schedule. However, to manually clean up queries on a need basis, you can use the Query Processor API. When you call this API, it also runs a VACUUM command on the Query Processor tables. All queries that were run before the epoch time are cleared. For more information, see Ways to clean up old queries from the Query Processor tables.
Hue uses the SHA-256 signing algorithm for SAML authentication
The SHA-1 signing algorithm is deprecated in most environments. Hue now uses a stronger, secure hash algorithm, SHA-256, for signature and digest methods when authenticating using SAML.
Update to the list of supported non-ASCII characters
Hue supports an additional set of non-ASCII characters. % is also supported for file and folder names on HDFS and object stores. See Supported non-ASCII and special characters in Hue for a complete list.
Hue supports Spark SQL using Apache Livy
Hue supports Spark 3 and Livy 3. You can now run Spark SQL queries from Hue. Apache Spark and Apache Livy services are installed on your CDP cluster when you add a Data Hub cluster using the Data Engineering cluster template. See Enabling Spark 3 engine in Hue.
Hue supports rolling restart
Hue service downtime is reduced from more than 30 minutes to approximately 80-90 seconds when you restart the CDP cluster in the rolling restart mode. When you restart only the Hue service, then Hue’s non-worker roles, such as the load balancer, Kerberos ticket renewer, and Hue server restart one after the other. For information about the rolling restart options, see Options to restart the Hue service.
Hue scripts included in CDP
CDP now includes Hue scripts that you can use for cleaning up old data, setting default editors, changing the document owners, and so on. You no longer need to clone the scripts from Cloudera’s GitHub repository. For more information, see Using Hue scripts.
Support for HiveServer2 (HS2) high availability
See Configuring Hue to handle HS2 failover.
No 64-character restriction on hostnames for Hue roles
Hue supports creating Hue role hostnames of more than 64 characters. There is no longer a restriction of 64 characters for the “BalancerMember Route” property.
Hue uses TLS 1.2 by default
Hue and Hue Load Balancer use TLS 1.2 or 1.3 by default. You no longer have to configure settings in Cloudera Manager to enforce TLS 1.2.