[AMBARI-13987] Set hive.metastore.schema.verification=true in hive-site.xml

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.2.0
• Component/s: ambari-server
• Assignee: Dmitry Lysnichenko
• Reporter: Dmitry Lysnichenko
• Created: 20/Nov/15 10:24
• Updated: 11/Apr/16 18:12
• Resolved: 20/Nov/15 10:51

Description

We would like to have the following settings in hive-site.xml for installs of 2.1 onwards -

hive.metastore.schema.verification=true

In addition, I think we may already have the following as the case, but just in case they aren't, I'd like to list the following two as well:

datanucleus.autoCreateSchema=false
datanucleus.fixedDatastore=true

Background:

The Hive metastore has an issue wherein it tries to be non-strict about the schema version of the metastore db, and it can try to update the schema version if it finds that it is itself a newer version.

This pairs well with things like autoCreateSchema, but since we're using SchemaTool to set up our schema, and at no point should we be allowing the metastore to update the schema itself, we would like to make sure that the schema validation step is a "strict" one, leading to metastore failure if the version number does not match, instead of the metastore simply updating the version.

In addition, there seems to be a bug when the database access is slow or unreliable where the metastore winds up creating multiple rows of entries in the schema table in some cases. (This seems to happen rarely, but with more occurrences on AzureDB than others)

Issue Links

• relates to: AMBARI-14775 Remove hive.metastore.schema.verification as part of base config properties
• links to: review_request_