[
https://issues.apache.org/jira/browse/HCATALOG-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267587#comment-13267587
]
Mithun Radhakrishnan commented on HCATALOG-389:
-----------------------------------------------
The second {{drop database}} is done as part of cleanup. It's for cases where
there is an unforeseen exception. The return code from this operation can be
safely ignored.
Your second point is something that occurred to us yesterday as well. We might
want to support using the hcat or hive cli to run the same. I'll introduce a
variable and defaults.
I'm working on Travis's comments as well.
> hcat_ping (script to check if HCatalog server is running/reachable)
> -------------------------------------------------------------------
>
> Key: HCATALOG-389
> URL: https://issues.apache.org/jira/browse/HCATALOG-389
> Project: HCatalog
> Issue Type: New Feature
> Components: client
> Affects Versions: 0.4.1
> Reporter: Mithun Radhakrishnan
> Assignee: Mithun Radhakrishnan
> Priority: Minor
> Fix For: 0.5
>
> Attachments: HCATALOG-389.patch
>
>
> It would be nice to have a script that checks if hcat_server is running,
> whether it's reachable and if it's "healthy". The current definition of
> "healthy" implies:
> 1. HCatalog responds to requests to list tables/databases.
> 2. Tables can be created/dropped in HCatalog.
> 3. When managed tables are used, table-directories are created/deleted on the
> DFS.
> 4. (Future:) ActiveMQ events are being posted correctly, when
> tables/partitions are created/dropped.
> Monitoring apps might use this script to detect when HCatalog is down.
> I'll post a trivial script that does 1-3, shortly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
