2.06 - Configuring the Hive Connector for Use with a Custom Hadoop Library Path or Custom JAR Path - Teradata QueryGrid

Teradata® QueryGrid™ Installation and User Guide

Product
Teradata QueryGrid
Release Number
2.06
Published
September 2018
Language
English (United States)
Last Update
2018-11-26
dita:mapPath
blo1527621308305.ditamap
dita:ditavalPath
ft:empty
If you installed Hadoop with a custom library path or stored any Hadoop .jar files listed in Hadoop JAR Files outside of the default Hadoop library, you must manually configure the Hive connector with the custom path for any files that do not reside in the default Hadoop library path.

If you need to add .jar files not listed in Hadoop JAR Files, you can manually configure the Hive connector to specify which path to use to find the .jar files.

This only affects the target Hive connector configuration and any files outside the default Hadoop path.
  1. Use the procedures in Editing a Connector or Editing a Link to enable either the Hadoop Library Path property or Custom JAR Path property, or both properties.
  2. Do one or both of the following:
    • In the Hadoop Library Path NVP, use comma-separated values to enter the custom library path or paths for all required .jar files not in the default Hadoop library path. If a custom path is provided, the default path is not used.
      /usr/hdp/2.3.4.0-3485/hive-hcatalog/share/hcatalog/,/usr/hdp/2.3.4.0-3485/hadoop-hdfs/,/usr/hdp/2.3.4.0-3485/hadoop-mapreduce
    • In the Custom JAR Path NVP, use comma-separated values to enter the paths for additional, custom JARs not listed in Hadoop JAR Files reside.
      /lib, /user/lib