[HIVE-14907] Hive Metastore should use repeatable-read consistency level

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.2.0
• Component/s: Metastore
• Assignee: Unassigned
• Reporter: Lenni Kuff
• Created: 07/Oct/16 01:59
• Updated: 17/May/23 23:03

Description

Currently HMS uses the "read-committed" consistency level which is the default for DataNucleus. This could cause potential problems since the state visible to each transaction can actually see updates from other transactions, so it is very difficult to reason about any code that reads multiple pieces of data.

Instead it should use "repeatable-read" consistency which guarantees that any transaction only sees the state at the beginning of a transaction plus any updates done within a transaction.

Issue Links

• is related to: IMPALA-8479 REFRESH may fail if table metadata mutates during load
• relates to: HIVE-16738 Notification ID generation in DBNotification might not be unique across HS2 instances.