Skip to main content
Pentaho Documentation

Set Up Pentaho to Connect to a Hortonworks Cluster

Overview

These instructions explain how to configure Pentaho's HDP shim, so Pentaho can connect to a working Hortonworks Data Platform (HDP) cluster. 

Before You Begin

Before you begin, you will need to do a few things.

  1. Verify Support
    Check the Components Reference to verify that your Pentaho version supports your version of the HDP cluster.
     
  2. Set Up a HDP cluster
    Pentaho can connect to secured and unsecured HDP Clusters:
    1. Configure a HDP cluster.  See Hortonwork's documentation if you need help.
    2. Install any required services and service client tools.
    3. Test the cluster.
       
  3. Get Connection Information
    Get connection information for the cluster and services that you will use from your Hadoop Administrator, or from Ambari or other cluster management tools.
     
  4. Add a YARN User to Superuser Group
    Add the YARN user on the cluster to the group defined by dfs.permissions.superusergroup property. The dfs.permissions.superusergroup property can be found in hdfs-site.xml file on your cluster or in the cluster management application.
     
  5. Review the Notes Section
    Read the Notes section to review special configuration instructions for your version of HDP.

If you are connecting to a secured HDP cluster there are a few additional things you need to do.

  1. Secure the HDP with Kerberos
    Pentaho supports Kerberos authentication.  You will need to:
    1. Configure Kerberos security on the cluster, including the Kerberos Realm, Kerberos KDC, and Kerberos Administrative Server.
    2. Configure the name, data, secondary name, job tracker, and task tracker nodes to accept remote connection requests.
    3. Set up Kerberos for name, data, secondary name, job tracker, and task tracker nodes if you are have deployed Hadoop using an enterprise-level program.
    4. Add the user account credential for each PDI client user that should have access to the Hadoop cluster to the Kerberos database.  Make sure there is an operating system user account on each node in the Hadoop cluster for each user that you want to add to the Kerberos database. Add operating system user accounts if necessary. Note that the user account UIDs must be greater than the minimum user ID value (min.user.id). Usually, the minimum user ID value is set to 1000.
       
  2. Set up Kerberos on your Pentaho computers
    Instructions for how to do this appear in Set Up Kerberos for Pentaho.

Edit Configuration Files on Clusters

Pentaho-specific edits to configuration files are the cluster are referenced in this section.

Oozie

The Oozie user runs Oozie jobs by default.  If you use PDI to start an Oozie job, you must add the PDI user to the oozie-site.xml file on the cluster so that the PDI user can execute the program in proxy. If you plan to use the Oozie service complete these instructions:

  1. Open the oozie-site.xml file on the cluster.
  2. Add the following lines of the code to the oozie-site.xml file on cluster, substituting <your_pdi_user_name> with the PDI User username, such as jdoe.
1    <property>
2    <name>oozie.service.ProxyUserService.proxyuser.<your_pdi_user_name>.groups</name>
3    <value>*</value>
4    </property>
5    <property>
6    <name>oozie.service.ProxyUserService.proxyuser.<your_pdi_user_name>.hosts</name>
7    <value>*</value>
8    </property>
  1. Save and close the file

Configure Pentaho Component Shims

You must configure the shim in each of the following Pentaho components, on each computer from which Pentaho will be used to connect to the cluster:

  • Spoon (PDI Client)
  • Pentaho Server, including Analyzer and Pentaho Interactive Reporting.
  • Pentaho Report Designer (PRD)
  • Pentaho Metadata Editor (PME)

As a best practice, configure the shim in the PDI client first.  The PDI client has features that will help you test your configuration. Then, copy the tested the PDI client configuration files to other components, making changes if necessary. 

You can also opt to go through these instructions for each Pentaho component, and not copy the shim files from the PDI client.  If you do not plan to connect to the cluster from the PDI client, you can configure the shim in another component first instead.   

Step 1: Locate the Pentaho Big Data Plugin and Shim Directories

Shims and other parts of the Pentaho Adaptive Big Data Layer are in the Pentaho Big Data Plugin directory.  The path to this directory differs by component. You need to know the locations of this directory, in each component, to complete shim configuration and testing tasks.

In the following table, <pentaho home> in the shim locations for each component is the directory where Pentaho is installed:

Components Location of Pentaho Big Data Plugin Directory
PDI client <pentaho home>/design-tools/data-integration/plugins/pentaho-big-data-plugin
Pentaho Server <pentaho home>/server/pentaho-server/pentaho-solutions/system/kettle/plugins/pentaho-big-data-plugin
Pentaho Report Designer <pentaho home>/design-tools/report-designer/plugins/pentaho-big-data-plugin
Pentaho Metadata Editor <pentaho home>/design-tools/metadata-editor/plugins/pentaho-big-data-plugin

Shims are located in the pentaho-big-data-plugin/hadoop-configurations directory.  Shim directory names consist of a three or four-letter Hadoop Distribution abbreviation followed by the Hadoop Distribution's version number.  The version number does not contain a decimal point.  For example, the shim directory named cdh512 is the shim for the CDH (Cloudera Distribution for Hadoop), version 5.12.  Here is a list of the shim directory abbreviations.

Abbreviation Shim
cdh Cloudera's Distribution of Apache Hadoop
emr Amazon Elastic Map Reduce
hdi Microsoft Azure HDInsight
hdp Hortonworks Data Platform
mapr MapR

Step 2: Select the Correct Shim

Although Pentaho often supports one or more versions of a Hadoop distribution, the download of the Pentaho Suite only contains the latest, supported, Pentaho-certified version of the shim.  The other supported versions of shims can be downloaded from the Pentaho Customer Support Portal

Before you begin, verify that the shim you want is supported by your version of Pentaho shown in the Components Reference.

  1. Navigate to the pentaho-big-data-plugin/hadoop-configurations directory to view the shim directories. If the shim you want to use is already there, you can go to Step 3: Copy the Configuration Files from Cluster to Shim
  2. On the Customer Portal home page, sign in using the Pentaho support user name and password provided to you in your Pentaho Welcome Packet. 
  3. In the search box, enter the name of the shim you want. Select the shim from the search results. Optionally, you can browse the shims by version on the Downloads page. 
  4. Read all prerequisites, warnings, and instructions. On the bottom of the page in the Box widget, click the shim zip file to download it. 
  5. Unzip the downloaded shim package into the pentaho-big-data-plugin/hadoop-configurations directory.

Step 3: Copy the Configuration Files from Cluster to Shim

Copying configuration files from the cluster to the shim helps keep key configuration settings in sync with the cluster and reduces configuration errors.

  1. Back up the existing HDP shim files in the pentaho-big-data-plugin/hadoop-configurations/hdpxx directory. 
  2. Copy the following configuration files from the HDP cluster to pentaho-big-data-plugin/hadoop-configurations/hdpxx (overwriting the existing files):
  • core-site.xml
  • hbase-site.xml
  • hdfs-site.xml
  • hive-site.xml
  • mapred-site.xml
  • yarn-site.xml

Step 4: Edit the Shim Configuration Files

You need to verify or change authentication, Oozie, Hive, MapReduce, and YARN settings in the following files:

  • core-site.xml
  • config.properties
  • hbase-site.xml
  • hive-site.xml
  • mapred-site.xml
  • yarn-site.xml

Verify or Edit config.properties (Unsecured Clusters)

If you are connecting to an unsecure cluster, verify that these values are properly set.  Set the Oozie proxy user if needed. 

  1. Navigate to the pentaho-big-data-plugin/hadoop-configurations/hdpxx directory and open config.properties.
  2. Add the following values:
Parameter Values
authentication.superuser.provider NO_AUTH
pentaho.oozie.proxy.user Add a proxy user's name to access the Oozie service through a proxy, otherwise, leave it set to oozie.
java.system.hdp.version HDP Version.  For HDP 2.2, this is 2.2.0.0-2041
  1. Save and close the file.

Edit config.properties (Secured Clusters)

If you are connecting to a secure cluster, add Kerberos information to the config.properties file. If you plan to use secure impersonation to access your cluster, see Use Secure Impersonation to Access a Hortonworks Cluster before editing the config.properties file.

Perform the following steps to add Kerberos information to the config.properties file: 

  1. Navigate to the pentaho-big-data-plugin/hadoop-configurations/hdpxx directory and open the config.properties file.
  2. Add the following values:
Parameter Values
authentication.superuser.provider hdp-kerberos (This should be the same as the authentication.kerberos.id.)
authentication.kerberos.principal Set the Kerberos principal.
authentication.kerberos.password Set the Kerberos password.  You only need to set the password or the keytab, not both.
authentication.kerberos.keytabLocation Set the Kerberos keytab.  You only need to set the password or the keytab, not both.
pentaho.oozie.proxy.user Add the proxy user's name if you plan to access the Oozie service through a proxy.  Otherwise, leave it set to oozie.
java.system.hdp.version HDP Version.  For HDP 2.2, this is 2.2.0.0-2041
  1. Save and close the file.

Edit hbase-site.xml

Edit the location of the temporary directory in the hbase-site.xml file to create an HBase local storage directory.

  1. Navigate to the pentaho-big-data-plugin/hadoop-configurations/hdpxx directory and open the hbase-site.xml file.
  2. Add the following value:
Parameter Value
hbase.tmp.dir  /tmp/hadoop/hbase
  1. Save and close the file.

Edit hive-site.xml

Verify that the following parameter is set in the hive-site.xml file:

  1. Navigate to the pentaho-big-data-plugin/hadoop-configurations/hdpxx directory and open the hive-site.xml file.
  2. Add the following value:
Parameter Value
hive.metastore.uris Set this to the location of your hive metastore. 
  1. Save and close the file.

Edit mapred-site.xml

Edit the mapred-site.xml file to indicate where the job history logs are stored and to allow MapReduce jobs to run across platforms. 

  1. Navigate to the pentaho-big-data-plugin/hadoop-configurations/hdpxx directory and open the mapred-site.xml file.
  2. Add the following values:
Parameter Value
mapreduce.jobhistory.address Set this to the folder where you want to store the job history logs.
mapreduce.application.classpath

Add classpath information. Here is an example:

<property>
	<name>mapreduce.application.classpath</name>
	<value>$PWD/mr-framework/hadoop/share/hadoop/mapreduce/*
			:$PWD/mr-framework/hadoop/share/hadoop/mapreduce/lib/*
			:$PWD/mr-framework/hadoop/share/hadoop/common/*:$PWD/mr-framework/hadoop/share/hadoop/common/lib/*
			:$PWD/mr-framework/hadoop/share/hadoop/yarn/*:$PWD/mr-framework/hadoop/share/hadoop/yarn/lib/*
			:$PWD/mr-framework/hadoop/share/hadoop/hdfs/*:$PWD/mr-framework/hadoop/share/hadoop/hdfs/lib/*
			:/usr/hdp/${hdp.version}/hadoop/lib/hadoop-lzo-0.6.0.${hdp.version}.jar:/etc/hadoop/conf/secure
	</value>
</property>

 

mapreduce.application.framework.path

Set the framework path.  Here is an example:

<property>
  <name>mapreduce.application.framework.path</name>
  <value>/hdp/apps/${hdp.version}/mapreduce/mapreduce.tar.gz#mr-framework</value>
</property>
  1. Verify the mapreduce.app-submission.cross-platform property is in the mapred-site.xml file. If it is not in the file, add it as follows.
Parameter Value
mapreduce.app-submission.cross-platform Add this property to allow MapReduce jobs to run on either Windows client or Linux server platforms.
<property>
  <name>mapreduce.app-submission.cross-platform</name>
  <value>true</value>
</property>
  1. Save and close the file.

Edit yarn-site.xml

Verify that the following parameters are set in the yarn-site.xml file.

  1. Navigate to the pentaho-big-data-plugin/hadoop-configurations/hdpxx directory and open the yarn-site.xml file.
  2. Add these values:
Parameter Values
yarn.application.classpath ​Add the classpaths needed to run YARN applications.  Use commas to separate multiple paths. 
Example:
<property> <name>yarn.application.classpath</name>
 <value>$HADOOP_CONF_DIR,/usr/hdp/current/hadoop-client/*,
/usr/hdp/current/hadoop-client/lib/*,/usr/hdp/current/hadoop-hdfs-client/*,
/usr/hdp/current/hadoop-hdfs-client/lib/*,/usr/hdp/current/hadoop-yarn-client/*,
/usr/hdp/current/hadoop-yarn-client/lib/*</value>
 </property>
 
yarn.resourcemanager.hostname Update the hostname in your environment or use the default: sandbox.hortonworks.com
yarn.resourcemanager.address Update the hostname and port for your environment.
yarn.resourcemanager.admin.address Update the hostname and port for your environment.
  1. Save and close the file.

Connect to a Hadoop Cluster with the PDI Client    

Once you have set up your shim, you must make it active, then configure and test the connection to the cluster. For details on setting up the connection, see the article Connect to a Hadoop Cluster with the PDI Client

Connect Other Pentaho Components to the Hortonworks Cluster

These instructions explain how to create and test a connection to the cluster in the Pentaho Server, PRD, and PME. Creating and testing a connection to the cluster in the PDI client involves two tasks:

  • Setting the active shim on PRD, PME, and the Pentaho Server
  • Configuring and testing the cluster connections 

Set the Active Shim on PRD, PME, and the Pentaho Server

Modify the plugin.properties file to set the active shim for the Pentaho Server, PRD, and PME.

  1. Stop the component.
  2. Locate the pentaho-big-data-plugin directory for your component. 
  3. Navigate to the hadoop-configurations directory.
  4. Navigate to the pentaho-big-data-plugin directory and open the plugin.properties file.
  5. Set the active.hadoop.configuration property to the directory name of the shim you want to make active.  Here is an example:
active.hadoop.configuation=hdp24
  1. Save and close the plugin.properties file.
  2. Restart the component.

Create and Test Connections

Connection tests appear in the following table.

Component Test
Pentaho Server for DI

Create a transformation in the PDI client and run it remotely.

Pentaho Server for BA Create a connection to the cluster in the Data Source Wizard.
PME Create a connection to the cluster in PME.
PRD Create a connection to the cluster in PRD.

 

Once you've connected to the cluster and its services properly, provide connection information to users who need access to the cluster and its services.  Those users can only obtain access from computers that have been properly configured to connect to the cluster.

Here is what they need to connect:

  • Hadoop Distribution and version of the cluster
  • HDFS, JobTracker, ZooKeeper, and Hive2/Impala Hostnames, IP addresses and port numbers
  • Oozie URL (if used)
  • Users also require the appropriate permissions to access the directories they need on HDFS.  This typically includes their home directory and any other required directories.

They might also need more information depending on the job entries, transformation steps, and services they use.  Here's a more detailed list of information that your users might need from you.

Notes

The following notes are special topics for HDP.

HDP 2.5 Notes

The following note address issues with HDP 2.5.

Sqoop Support

If you receive an error message stating Generating splits for a textual index column allowed only in case of "-Dorg.apache.sqoop.splitter.allow_text_splitter=true" property passed as a parameter while trying to use the split-by option to the Sqoop Import job entry with the HDP 2.5 shim, perform the following steps to set the org.apache.sqoop.splitter.allow_text_splitter property to true:

  1. Open your KJB file that contains a Sqoop Import entry in the PDI client.

  2. Double-click the Sqoop Import entry to access the Sqoop Import property dialog box.

  3. Click the Advanced Options link in the lower left corner of the dialog box.

  4. In the Custom tab, add the Dorg.apache.sqoop.splitter.allow_text_splitter argument and set the value to true.

  5. Click OK and save your KJB file.

You should now be able to use the split-by option to the Sqoop Import entry.

Java System HDP Version

The config.properties file in the HDP 2.5 shim contains a property and value which is currently set to:  

 java.system.hdp.version=2.5.0.0-1245

If this property and the exact version number is not set correctly to match the version of HDP 2.5 that is running in your Pentaho system, your Pentaho map reduce jobs will fail.

Pentaho uses this property and version parameter to locate a folder in the /hdp/apps folder on hdfs that contains dependencies needed to run the map reduce job. You can determine the current value of this property by logging into the cluster and issuing the command:

 hadoop fs -ls /hdp/apps

The resulting output should be similar to:

Found 1 items
drwxr-xr-x   - hdfs hdfs          0 2017-02-16 11:03 /hdp/apps/2.5.3.0-37

In the example above, the correct setting for the property and version number line is:

java.system.hdp.version=2.5.3.0-37

You must edit your config.properties file to update the java.system.hdp property with the exact version number of HDP 2.5 that is running in your Pentaho system.

HDP 2.4 Notes

The following note address issues with HDP 2.4.

Simba Spark SQL Driver Support

If you are using Pentaho 7.0 or later, the HDP 2.4 shim supports the Simba Spark SQL driver. You will need to download, install, and configure the driver to use Simba Spark SQL with the HDP 2.4 shim.

  1. Download the Simba Spark SQL driver.
  2. Extract the ZIP file, and then copy the following 3 files into the lib/ directory of the HDP shim:
  • SparkJDBC41.jar
  • TCLIServiceClient.jar
  • QI.jar
  1. In the Database Connection window, select SparkSQL option. The default port for the Spark thrift server is 10015.
  2. For secure connections, set the following additional parameters on the JDBC URL through the Options tab:

  • KrbServiceName
  • KrbHostFQDN
  • KrbRealm
  1. For unsecure connections, if your Spark SQL configuration specifies hive.server2.authentication=NONE, then make sure to include an appropriate User Name in the Database Connection window.  Otherwise, the connection is assumed to be NOSASL authentication, which will cause a connection failure after timeout.

  2. Stop and restart the component.

HDP 2.3 Notes

The following note addresses issues with HDP 2.3.

Pentaho can connect to HDP 2.3 cluster using the HDP 2.2 or HDP 2.3 shims

You can use either the HDP 2.2 or HDP 2.3 shims to connect to a HDP 2.3 clusters:

  • If you use the HDP 2.2 shim to connect to an HDP 2.3 cluster, only HDP 2.2 functionality is supported. 
  • If you want to support HDP 2.3 functionality, use the HDP 2.3 shim to connect to the HDP 2.3 cluster instead.

Shims can be downloaded from the Pentaho Customer Support Portal.

For troubleshooting cluster and service configuration Issues, refer to Big Data Issues.