You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Aleksandr Kovalenko (JIRA)" <ji...@apache.org> on 2015/08/20 15:25:45 UTC
[jira] [Commented] (AMBARI-12830) SQLA: UI fixes for oozie SQLA db
[ https://issues.apache.org/jira/browse/AMBARI-12830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704868#comment-14704868 ]
Aleksandr Kovalenko commented on AMBARI-12830:
----------------------------------------------
+1 for the patch
> 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
>
> Attachments: AMBARI-12830.patch
>
>
> 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}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)