ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitalyi Brodetskyi" <>
Subject Re: Review Request 21160: Usability: performing connectivity checks against an external database
Date Fri, 23 May 2014 14:33:26 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated May 23, 2014, 2:33 p.m.)

Review request for Ambari, Dmitro Lisnichenko and Mahadev Konar.


Second part of changes! Please review it. Ticket for tests i'll create later.

Bugs: AMBARI-5696

Repository: ambari


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


  ambari-server/src/main/python/ 81dadbd 
  ambari-server/src/main/resources/custom_actions/ e5aa920 



Listening for transport dt_socket at address: 5007
Running org.apache.ambari.server.view.RemoteDBConnectionVerificator.RemoteDBConnectionVerificatorTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.247 sec

Results :

Tests run: 3, Failures: 0, Errors: 0, Skipped: 0


Vitalyi Brodetskyi

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message