Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Hive Config variables Session vs XML

avatar
Rising Star

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

avatar

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.

View solution in original post

1 REPLY 1

avatar

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.