Versions Compared

Old Version 39

changes.mady.by.user Lefty Leverenz

Saved on

compared with

New Version 40

changes.mady.by.user Thejas Nair

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: making it bit easier to find doc of server specific config files

...

A number of configuration variables in Hive can be used by the administrator to change the behavior for their installations and user sessions. These variables can be configured in any of the following ways, shown in the order of preference:

  • Using the set command in the CLI or Beeline for setting session level values for the configuration variable for all statements subsequent to the set command. For example, the following command sets the scratch directory (which is used by Hive to store temporary output and plans) to /tmp/mydir for all subsequent statements:

    No Format
      set hive.exec.scratchdir=/tmp/mydir;

  • Using the --hiveconf option of the hive command (in the CLI) or beeline command for the entire session. For example:

    No Format
      bin/hive --hiveconf hive.exec.scratchdir=/tmp/mydir

  • In hive-site.xml. This is used for setting values for the entire Hive configuration (see hive-site.xml and hive-default.xml.template below). For example:

    No Format
      <property>
    <name>hive.exec.scratchdir</name>
    <value>/tmp/mydir</value>
    <description>Scratch space for Hive jobs</description>
  </property>
  • In server-specific configuration files (supported starting Hive 0.14). You can set metastore-specific configuration values in hivemetastore-site.xml, and HiveServer2-specific configuration values in hiveserver2-site.xml.
    The server-specific configuration file is useful in two situations:

...