Return-Path: X-Original-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AA3F310CFE for ; Wed, 16 Oct 2013 17:47:49 +0000 (UTC) Received: (qmail 99838 invoked by uid 500); 16 Oct 2013 17:47:46 -0000 Delivered-To: apmail-incubator-ambari-dev-archive@incubator.apache.org Received: (qmail 99738 invoked by uid 500); 16 Oct 2013 17:47:43 -0000 Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ambari-dev@incubator.apache.org Delivered-To: mailing list ambari-dev@incubator.apache.org Received: (qmail 99651 invoked by uid 99); 16 Oct 2013 17:47:42 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Oct 2013 17:47:42 +0000 Date: Wed, 16 Oct 2013 17:47:42 +0000 (UTC) From: "Mahadev konar (JIRA)" To: ambari-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-3530) Backend support to perform database connectivity testing for Hive/Oozie DB Config/Reconfig MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797047#comment-13797047 ] Mahadev konar commented on AMBARI-3530: --------------------------------------- Looks like Nate/Tom brought up a good point wherein the API would be throw away once we have custome actions. Vitaly, we can just do 2) for now and wait for custom actions to provide a better and cleaner API for checks. > 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 > > > 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)