You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2013/09/05 20:38:51 UTC
[jira] [Updated] (HIVE-5228) exceptions regarding
NonExistentDatabaseUsedForHealthCheck are extremely annoying
[ https://issues.apache.org/jira/browse/HIVE-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Shelukhin updated HIVE-5228:
-----------------------------------
Description: There are bunch of exceptions in the logs of many tests, with long call stacks, regarding NonExistentDatabaseUsedForHealthCheck. This is coming from CacheableHiveMetaStoreClient. Perhaps it could do something better for health check, like remember last database that was used and use that instead. I am not familiar with the code so I would assume this health check is actually useful. (was: There are bunch of exceptions in the logs of many tests, with long call stacks, regarding NonExistentDatabaseUsedForHealthCheck. This is coming from CacheableHiveMetaStoreClient. Perhaps it could so something better for health check, like remember last database that was used and use that instead. I am not familiar with the code so I would assume this health check is actually useful.)
> exceptions regarding NonExistentDatabaseUsedForHealthCheck are extremely annoying
> ---------------------------------------------------------------------------------
>
> Key: HIVE-5228
> URL: https://issues.apache.org/jira/browse/HIVE-5228
> Project: Hive
> Issue Type: Improvement
> Reporter: Sergey Shelukhin
>
> There are bunch of exceptions in the logs of many tests, with long call stacks, regarding NonExistentDatabaseUsedForHealthCheck. This is coming from CacheableHiveMetaStoreClient. Perhaps it could do something better for health check, like remember last database that was used and use that instead. I am not familiar with the code so I would assume this health check is actually useful.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira