[HIVE-24453] Direct SQL error when parsing create_time value for database

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.0-alpha-1
• Component/s: Metastore
• Labels: pull-request-available
• Assignee: Jesús Camacho Rodríguez
• Reporter: Jesús Camacho Rodríguez
• Created: 30/Nov/20 20:26
• Updated: 27/Feb/24 22:23
• Resolved: 02/Dec/20 15:56

Description

HIVE-21077 introduced a create_time field for DBS table in HMS. Although the value for that field is always set after that patch, the value could be null if the database was created before the feature went in. DirectSQL should check for null value before parsing the integer, otherwise we hit an exception and fallback to ORM path:

2020-11-28 09:06:05,414 WARN  org.apache.hadoop.hive.metastore.ObjectStore: [pool-8-thread-194]: Falling back to ORM path due to direct SQL failure (this is not an error): null at org.apache.hadoop.hive.metastore.MetastoreDirectSqlUtils.extractSqlInt(MetastoreDirectSqlUtils.java:251) at org.apache.hadoop.hive.metastore.MetaStoreDirectSql.getDatabase(MetaStoreDirectSql.java:420) at org.apache.hadoop.hive.metastore.ObjectStore$1.getSqlResult(ObjectStore.java:839)

Issue Links

• relates to: HIVE-21077 Database and catalogs should have creation time
• links to: GitHub Pull Request #1719