ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrii Babiichuk (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-12830) SQLA: UI fixes for oozie SQLA db
Date Thu, 20 Aug 2015 13:23:45 GMT
Andrii Babiichuk created AMBARI-12830:
-----------------------------------------

             Summary: SQLA: UI fixes for oozie SQLA db
                 Key: AMBARI-12830
                 URL: https://issues.apache.org/jira/browse/AMBARI-12830
             Project: Ambari
          Issue Type: Bug
          Components: ambari-web
    Affects Versions: 2.1.2
            Reporter: Andrii Babiichuk
            Assignee: Andrii Babiichuk
            Priority: Critical
             Fix For: 2.1.2


1) When we are choosing SQLA db on Customize service step, warning appears:
{code}
Be sure you have run:
ambari-server setup --jdbc-db=sqla --jdbc-driver=/path/to/sqla/driver.jar on the Ambari Server
host to make the JDBC driver available and to enable testing the database connection.
{code}
For SQLA we are using type2 jdbc, and user should set something like 
{{ambari-server setup --jdbc-db=sqlanywhere --jdbc-driver=/path/to/sqla-client-jdbc.tar.gz}}

2) Oozie hangs on start of deploy. Looks like it's some problem on UI with oozie properties.

3) Db url for SQLA need additional fields. For now we have:
{code}
jdbc:sqlanywhere:database=oozie;host=vitaha-1.c.pramod-thangali.internal
{code}
but url should contain username and password too:
{code}
jdbc:sqlanywhere:uid={username};pwd={password};database=oozie;host=vitaha-1.c.pramod-thangali.internal
{code}

[~smohanty]/[~jluniya], feel free to change/correct description if i'm not right.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message