Description of problem ====================== Based on the BZ 1118806 (see Brad's comment 30 there), additional configuration is required for Hive to work properly: > Solution to HIVE issue: > > HIVE will propagate permissions with this: > > set hive.warehouse.subdir.inherit.perms = true as custom property in hive-site.xml during ambari configuration. > > permission of glusterfs:///apps/hive/warehouse should be 0775 > > HIVE will propagate parent 775 permissions to the warehouse sub directories Since the installer aready creates warehouse directory, it makes sense to implement this Hive configuration in the installer. Version-Release number of selected component (if applicable) ============================================================ rhs-hadoop-install-2_47-1.el6rhs.noarch Steps to Reproduce ================== 1. install rhs-hadoop cluster using rhs-hadoop-install scripts 2. make sure you install Hive (when Hadoop cluster is created in Ambari) Actual results ============== Hive property `hive.warehouse.subdir.inherit.perms` is undefined. Access rights on warehouse directory are set to 755: ~~~ $ hadoop fs -ls -d /apps/hive/warehouse 2>/dev/null drwxr-xr-x - hive hadoop 30 2015-04-29 13:48 /apps/hive/warehouse ~~~ Expected results ================ Hive property `hive.warehouse.subdir.inherit.perms` is set to true. Access rights on warehouse directory are set to 775: ~~~ $ hadoop fs -ls -d /apps/hive/warehouse 2>/dev/null drwxrwxr-x - hive hadoop 30 2015-04-29 13:48 /apps/hive/warehouse ~~~ Additional info =============== To properly verify this issue, run Hive reproducer from comment 2 of BZ 1118806.
The installer does set perms/owner on required hadoop directories, and it also sets 2 core-site properties related to enabling/disabling volumes. However, most of the core-site, yarn-site properties that are special for rhs are set by Ambari. Why shouldn't the property mentioned in this BZ also be set by Ambari?
per conversation with Erin I transferred this to Ambari.
(In reply to Jeff Vance from comment #1) > The installer does set perms/owner on required hadoop directories, and it > also sets 2 core-site properties related to enabling/disabling volumes. > However, most of the core-site, yarn-site properties that are special for > rhs are set by Ambari. Why shouldn't the property mentioned in this BZ also > be set by Ambari? That's a good point, you are right. Installer should do this only if we fail to add hive.warehouse.subdir.inherit.perms property into GlusterFS stack in Ambari.
Fixed in 2.3
This solution is no longer available from Red Hat.