You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Jesus Camacho Rodriguez (Jira)" <ji...@apache.org> on 2020/11/30 20:27:00 UTC
[jira] [Assigned] (HIVE-24453) DirectSQL error when parsing
create_time value for database
[ https://issues.apache.org/jira/browse/HIVE-24453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesus Camacho Rodriguez reassigned HIVE-24453:
----------------------------------------------
> DirectSQL error when parsing create_time value for database
> -----------------------------------------------------------
>
> Key: HIVE-24453
> URL: https://issues.apache.org/jira/browse/HIVE-24453
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Priority: Major
>
> 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:
> {noformat}
> 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)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)