[
https://issues.apache.org/jira/browse/AMBARI-23620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449900#comment-16449900
]
Hudson commented on AMBARI-23620:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9105 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9105/])
AMBARI-23620. Moving DB condifuration related code to common Service
(m.magyar3:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=c9d9f03493a81572d7234447d10f57815d4fc870])
* (edit) ambari-server/src/main/resources/stacks/service_advisor.py
> Oozie - JDBC Driver class does not change when the Database type is changed
> ---------------------------------------------------------------------------
>
> Key: AMBARI-23620
> URL: https://issues.apache.org/jira/browse/AMBARI-23620
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.7.0
> Reporter: Srikanth Janardhan
> Assignee: Sandor Molnar
> Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: db-config-issues.mov
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> In ambari 2.7.0.0-330, when the database type is changed for Oozie service,
> the JDBC server class does not change. This happens in the install wizard as
> well as post-install.
> The behavior is different in Hive, where the JDBC server class changes when
> the database type changes
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
