Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Hive Config variables Session vs XML

Solved Go to solution

Hive Config variables Session vs XML

New Contributor

Does anyone know of how to track what Hive config variables are able to be set at the session level vs which are required to be set at the config xml level (and require a restart of the component)?

Hive Config Java provides a list of most Hive variables, but there seems to be no easy way to tell.

e.g. There are multiple hive.metastore.* variables that only can be set in the config XML and require a Hive Metastore restart.

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Hive Config variables Session vs XML

Master Collaborator

Unfortunately there is no clear standard that has been followed on naming client side vs server side properties. hive.metastore.* as the name suggests would be Hive metastore server side properties, similarly hive.server2.* would be HiveServer2 server side properties. However whitelisted properties listed as part of SQL Standard Authorization can be used as cue, these are client side properties that the end user is allowed to set when running under the SQL Standard authorization configuration.

1 REPLY 1

Re: Hive Config variables Session vs XML

Master Collaborator

Unfortunately there is no clear standard that has been followed on naming client side vs server side properties. hive.metastore.* as the name suggests would be Hive metastore server side properties, similarly hive.server2.* would be HiveServer2 server side properties. However whitelisted properties listed as part of SQL Standard Authorization can be used as cue, these are client side properties that the end user is allowed to set when running under the SQL Standard authorization configuration.