[
https://issues.apache.org/jira/browse/FALCON-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063193#comment-14063193
]
Venkatesh Seetharam commented on FALCON-507:
--------------------------------------------
Bosco reported: I tried dropping the “default” DB and it failed.
{code}
hive> drop database default cascade;
FAILED: Execution Error, return code 1 from
org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:Can not drop
default database)
{code}
Looks like we should be fine. A better alternate would be to list databases
than fetching a specific one.
[~sushanth], [~thejas], thoughts?
> HiveCatalogService has hardcode the database name "default" to check whether
> the service is up.
> ------------------------------------------------------------------------------------------------
>
> Key: FALCON-507
> URL: https://issues.apache.org/jira/browse/FALCON-507
> Project: Falcon
> Issue Type: Bug
> Affects Versions: 0.5
> Reporter: Venkatesh Seetharam
> Labels: hive
> Fix For: 0.6
>
>
> Don Bosco Durai reported in an email to me:
> While debugging the issue, it seems HiveCatalogService has hardcode the
> database name "default" to check whether the service is up. I think this
> check will fail if the customer has dropped the database "default" in
> production.
> {code}
> @Override
> public boolean isAlive(final String catalogUrl,
> final String metaStorePrincipal) throws
> FalconException {
> LOG.info("Checking if the service is alive for: " + catalogUrl);
> try {
> HCatClient client = getProxiedClient(catalogUrl,
> metaStorePrincipal);
> HCatDatabase database = client.getDatabase("default");
> return database != null;
> } catch (HCatException e) {
> throw new FalconException("Exception checking if the service is
> alive:" + e.getMessage(), e);
> }
> }
> {code}
> Thanks Bosco.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
