Steps to build a release version of Hortonworks component. Component details in question. Component Name = Hadoop Release Version = 2.3.4.0 Tools Needed: Maven = 3.1.1 Java = 1.7+ Steps: 1. Ensure Java and Maven is in path. 2. Get the code to your local linux machine, say workspace. $ git clone git@github.com:hortonworks/hadoop-release.git -b HDP-2.3.4.0-tag Hortonworks maintain <component>-release tags for all the public releases. 3. Point maven settings.xml to http://repo.hortonworks.com/content/groups/public/ 4. Go to the synced workspace and issue below command $ maven clean -DskipTests -DskipITs install Cheers, -Vijay. ... View more

This can be solved by appending "oozie.launcher." to the properties. <configuration> <property> <name>oozie.launcher.dfs.nameservices</name> <value>${nameService1},${nameService2}</value> </property> <property> <name>oozie.launcher.dfs.ha.namenodes.${nameService2}</name> <value>${nn21},${nn22}</value> </property> <property> <name>oozie.launcher.dfs.namenode.rpc-address.${nameService2}.${nn21}</name> <value>${nn21_fqdn}:8020</value> </property> <property> <name>oozie.launcher.dfs.namenode.rpc-address.${nameService2}.${nn22}</name> <value>${nn22_fqdn}:8020</value> </property> <property> <name>oozie.launcher.dfs.client.failover.proxy.provider.${nameService2}</name> <value>org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider</value> </property> <property> <name>oozie.launcher.mapreduce.job.hdfs-servers</name> <value>${defaultFS1},${defaultFS2}</value> </property> </configuration> ... View more

ODBC Driver v2.0.5 (released with HDP 2.3) is tested and compatible with Windows 2012 and also backward compatible with HDP 2.2. The driver supports Hive 0.11, 0.12, 0.13, 0.14, 1.0, 1.1, and 1.2. http://hortonworks.com/products/releases/hdp-2-3/#add_ons ... View more

Does this question refer to Hadoop Service Level Authorization? http://hadoop.apache.org/docs/r2.7.1/hadoop-project-dist/hadoop-common/ServiceLevelAuth.html If so, then there is no need to restart the NameNode to make changes in service-level ACLs take effect. Instead, an admin can run this command: hdfs dfsadmin -refreshServiceAcl More documentation on this command is available here: http://hadoop.apache.org/docs/r2.7.1/hadoop-project-dist/hadoop-hdfs/HDFSCommands.html#dfsadmin There is similar functionality for YARN too: http://hadoop.apache.org/docs/r2.7.1/hadoop-yarn/hadoop-yarn-site/YarnCommands.html#rmadmin Another way to manage this is to declare a single "hadoopaccess" group for use in the service-level ACL definitions. Whenever a new set of users needs access, they would be added to this group. This shifts the management effort to an AD/LDAP administrator. Different IT shops would likely make a different trade-off between managing it that way or managing it in the service-level authorization policy files. Both approaches are valid, and it depends on the operator's preference. ... View more