ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitaly Brodetskyi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-5696) Usability: performing connectivity checks against an external database
Date Wed, 28 May 2014 16:10:06 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vitaly Brodetskyi updated AMBARI-5696:
--------------------------------------

    Attachment:     (was: AMBARI-5696_part_2.patch)

> 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)

Mime
View raw message