You will need to upgrade any custom applications after you upgrade to CDH 5.4.0.
In HUE-1859, the LDAP synchronization backend was moved to a generic middleware. If your code
uses DesktopSynchronizationBackendBase, you will need to create your own middleware, and extend the new LdapSynchronizationMiddleware. Put that new custom middleware class in the middleware= line of the [desktop] section of hue.ini. The following example uses a middleware called desktop.auth.backend.my_middleware.
# Comma-separated list of Django middleware classes to use.
# See https://docs.djangoproject.com/en/1.4/ref/middleware/ for more details on middlewares in Django.
HUE-1658 [oozie] Hue depends on OOZIE-1306 which is in CDH 5 Beta 2 but has not been included in any other release yet. Set the following backward compatibility
flag to false to use the old frequency number/unit representation instead of the new crontab.
enable_cron_scheduling = false
Hue 3.0.0 was a major revision of Hue. The user interface changed significantly.
CDH 5 Hue works only with the default system Python version of the operating system it is being installed on. For example, on RHEL/CentOS 6,
you need Python 2.6 to start Hue.
The Beeswax daemon has been replaced by HiveServer2. Hue should therefore point to a running HiveServer2. This change involves removing the Beeswaxd code entirely and the following
major updates to the [beeswax] section of the Hue configuration file, hue.ini.
# Host where Hive server Thrift daemon is running.
# If Kerberos security is enabled, use fully-qualified domain name (FQDN).
## hive_server_host=<FQDN of Hive Server>
# Port where HiveServer2 Thrift server runs on.
Search bind authentication is now used by default instead of direct bind. To revert to the previous settings, use the new search_bind_authentication