Release Notes
Also available as:

Behavioral Changes

Behavioral changes denote a marked change in behavior from the previously released version to this version of software. In HDP 2.6.1, behavioral changes affect the following Hadoop components.

Table 1.4. Behavioral Changes

Hortonworks Bug IDApache ComponentApache JIRASummaryDetails
BUG-66121HiveHIVE-14251 Union All of different types resolves to incorrect data

Scenario: UNION result handling

Previous Behavior: queries in which union operator was used may have created an invalid output type.for example, the column type is ambigous in the following query:

select cast(1 as int) union select cast(1 as string)

Selecting the inappropriate type may cause the value to be changed to NULL.

New Behavior: The types are checked prior to execution; and the ambigous cases are rejected;

FAILED: SemanticException Schema of both sides of union should match: Column _c0 is of type int on first table and type string on second table. Cannot tell the position of null AST. (state=42000,code=40000)

The query should be clarified with explicit casts.

BUG-76637RangerRANGER-1436Turn Ranger Deny Policy & Except Conditions block to Off by default

Component Affected: Ranger resource based policies

Previous Behavior: Previously, you could not enable deny/exception conditions through a configuration change. This was only possible through a Ranger REST API call.

New Behavior: You can now turn this feature on by setting the ranger.servicedef.enableDenyAndExceptionsInPolicies config parameter to a value of true. The default value for this is false (disabled).

BUG-81924Falcon, HveN/AUse the hive.metastore.transactional.event.listeners configuration parameter instead of hive.metastore.event.listeners

Component Affected: HiveDR replication on Falcon

Scenario: Although both parameters perform similar functions, hive.metastore.transactional.event.listeners provides better handling of failures for Falcon-Hive integration.

Previous Behavior: If HiveDR was enabled on a cluster, then the setting hive.metastore.event.listeners had to be set with the value org.apache.hive.hcatalog.listener.DbNotificationListener

New Behavior: If HiveDR is enabled, DbNotificationListener should belong to hive.metastore.transactional.event.listeners.

Do the following in hive-site.xml:

  1. Set hive.metastore.transactional.event.listeners="org.apache.hive.hcatalog.listener.DbNotificationListener"

  2. If set, remove hive.metastore.event.listeners="org.apache.hive.hcatalog.listener.DbNotificationListener"

BUG-91290Hive, RangerN/AAdditional ranger hive policies required for INSERT OVERWRITE

Scenario:Additional ranger hive policies required for INSERT OVERWRITE

Previous behavior: Hive INSERT OVERWRITE queries succeed as usual.

New behavior: Hive INSERT OVERWRITE queries are unexpectedly failing after upgrading to HDP-2.6.x with the error:

Error while compiling statement: FAILED: HiveAccessControlException Permission denied: user jdoe does not have WRITE privilege on /tmp/*(state=42000,code=40000)

As of HDP-2.6.0, Hive INSERT OVERWRITE queries require a Ranger URI policy to allow write operations, even if the user has write privilege granted through HDFS policy.

Workaround/Expected Customer Action:

  1. Create a new policy under the Hive repository.

  2. In the dropdown where you see Database, select URI.

  3. Update the path (Example: /tmp/*)

  4. Add the users and group and save.

  5. Retry the insert query.