You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Oleksandr Diachenko (JIRA)" <ji...@apache.org> on 2013/10/23 14:13:43 UTC

[jira] [Resolved] (AMBARI-3530) Backend support to perform database connectivity testing for Hive/Oozie DB Config/Reconfig

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

Oleksandr Diachenko resolved AMBARI-3530.
-----------------------------------------

    Resolution: Fixed

Commited to trunk.

> Backend support to perform database connectivity testing for Hive/Oozie DB Config/Reconfig
> ------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-3530
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3530
>             Project: Ambari
>          Issue Type: Improvement
>          Components: agent
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 1.4.2
>
>         Attachments: AMBARI-3530.patch
>
>
> The idea behind performing DB connection verification is for 2 things:
> 1. Before we even install on the UI we can provide a verification button taht allows for the user to confirm that he created the users and setup the DB correctly.
> 2. When installing/starting we can also make some checks to make sure when the process starts it will be ok and will not fail due to some jdbc connection issues.
> Both solve the same problem but do at different steps for building confidence in the setup process.



--
This message was sent by Atlassian JIRA
(v6.1#6144)