[
https://issues.apache.org/jira/browse/AMBARI-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi resolved AMBARI-5696.
---------------------------------------
Resolution: Fixed
Committed to trunk
> Usability: performing connectivity checks against an external database
> ----------------------------------------------------------------------
>
> Key: AMBARI-5696
> URL: https://issues.apache.org/jira/browse/AMBARI-5696
> Project: Ambari
> Issue Type: Task
> Components: agent
> Affects Versions: 1.6.0
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Fix For: 1.6.1
>
> Attachments: AMBARI-5696_part_1.patch, AMBARI-5696_part_2.patch
>
>
> Hive/Oozie (and possibly other components in the future) make use of a
> relational database to store its metadata.
> When the user wants to use an existing, external database, it's easy to
> mistype the credentials/JDBC string. Currently, such mistakes are not caught
> until service install or start, at which point it's a pain to reconfigure and
> fix the issue.
> API should expose the ability to check database connectivity given the JDBC
> connection string, username, and password, so that the UI can expose this to
> the end user in the Customize Services page.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
