Edit configuration files for users

Cloudera administrators download site configuration files for the services you use. They update the files with Pentaho-specific and user-specific settings. Users then upload the files when they create a named connection.

Named connection files are stored in these locations:

• <username>/.pentaho/metastore/pentaho/NamedCluster
• <username>/.pentaho/metastore/pentaho/NamedCluster/Configs/<connection-name>/config.properties

Save the updated files in a known location for reuse.

Files to provide

• config.properties
• core-site.xml (secured CDP only)
• hive-site.xml
• mapred-site.xml
• yarn-site.xml

If you update configuration files after creating a named connection, edit the named connection and re-upload the updated files.

Edit Core site XML file

If you use a secured instance of CDP, update core-site.xml.

1. Open core-site.xml.
2. Add or update these properties:

   Property	Value
   hadoop.proxyuser.oozie.hosts	Oozie hosts on your CDP cluster.
   hadoop.proxyuser.oozie.groups	Oozie groups on your CDP cluster.
   hadoop.proxyuser.<security_service>.hosts	Proxy user hosts for other services on your CDP cluster.
   hadoop.proxyuser.<security_service>.groups	Proxy user groups for other services on your CDP cluster.
   fs.s3a.access.key	Your S3 access key, if you access S3 from CDP.
   fs.s3a.secret.key	Your S3 secret key, if you access S3 from CDP.

3. Optional (AWS): If you connect to CDP Public Cloud on AWS and use an S3 bucket outside the CDP environment, update or add these properties:

   <property>
     <name>fs.s3a.delegation.token.binding</name>
     <value>org.apache.hadoop.fs.s3a.auth.delegation.SessionTokenBinding</value>
   </property>

   <property>
     <name>fs.s3a.aws.credentials.provider</name>
     <value>com.amazonaws.auth.InstanceProfileCredentialsProvider</value>
   </property>

   Ensure the gateway node has valid AWS credentials (for example, under ~/.aws/).
4. Optional (Azure): If you connect to CDP Public Cloud on Azure and use a storage account outside the CDP environment:

   • Remove these properties:

     • fs.azure.enable.delegation.token
     • fs.azure.delegation.token.provider.type
     • fs.azure.account.auth.type
     • fs.azure.account.oauth.provider.type
   • Add these properties:

     • fs.azure.account.auth.type.<storage-account-name>.dfs.core.windows.net = SharedKey
     • fs.azure.account.key.<storage-account-name>.dfs.core.windows.net = <storage-account-key>
5. Optional (GCP): If you connect to CDP Public Cloud on GCP and use a bucket outside the CDP environment, create a custom role with these permissions:

   storage.bucket.get
   storage.objects.create
   storage.objects.delete
   storage.objects.get
   storage.objects.getIamPolicy
   storage.objects.list
   storage.objects.setIamPolicy
   storage.objects.update

   Assign the custom role to the Data Lake and Log service accounts for the bucket.
6. Save the file.

Edit Hive site XML file

If you use Hive, update hive-site.xml to set the Hive metastore location.

1. Open hive-site.xml.
2. Add or update these properties:

   Property	Value
   hive.metastore.uris	Set this to the Hive metastore URI if it differs from your CDP cluster.
   hive.server2.enable.impersonation	Set to true if you use impersonation.
   hive.server2.enable.doAs	Set to true if you use impersonation.
   tez.lib.uris	Required when you use Hive 3 on Tez.

   Example:

   <property>
     <name>hive.server2.enable.doAs</name>
     <value>true</value>
   </property>

   <property>
     <name>tez.lib.uris</name>
     <value>/user/tez/0.9.1.7.1.4.0-203/tez.tar.gz</value>
   </property>

3. Save the file.

Edit Mapred site XML file

If you use MapReduce, update mapred-site.xml to set job history logging and allow cross-platform submissions.

1. Open mapred-site.xml.
2. Ensure these properties exist. Add them if needed:

   Property	Value
   mapreduce.jobhistory.address	Where MapReduce job history logs are stored.
   mapreduce.app-submission.cross-platform	Set to true to allow submissions from Windows clients to Linux servers.

   Example:

   <property>
     <name>mapreduce.app-submission.cross-platform</name>
     <value>true</value>
   </property>

3. Save the file.

Edit YARN site XML file

If you use YARN, verify your YARN settings in yarn-site.xml.

1. Open yarn-site.xml.
2. Add or update these properties:

   Property	Value
   yarn.application.classpath	Classpaths needed to run YARN applications. Use commas to separate multiple paths.
   yarn.resourcemanager.hostname	Resource Manager host name for your environment.
   yarn.resourcemanager.address	Resource Manager address and port for your environment.
   yarn.resourcemanager.admin.address	Resource Manager admin address and port for your environment.
   yarn.resourcemanager.proxy-user-privileges.enabled	Set to true if you use a proxy user.

   Example:

   <property>
     <name>yarn.resourcemanager.proxy-user-privileges.enabled</name>
     <value>true</value>
   </property>

3. Save the file.

After you change these files, edit the named connection and upload the updated files.