[
https://issues.apache.org/jira/browse/AMBARI-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako updated AMBARI-2466:
--------------------------------
Attachment: AMBARI-2466_upgrade_path.patch
> Hive/Oozie database settings should accept custom JDBC URLs
> -----------------------------------------------------------
>
> Key: AMBARI-2466
> URL: https://issues.apache.org/jira/browse/AMBARI-2466
> Project: Ambari
> Issue Type: Bug
> Components: client
> Affects Versions: 1.2.4
> Reporter: Yusaku Sako
> Assignee: Yusaku Sako
> Priority: Critical
> Fix For: 1.2.4
>
> Attachments: AMBARI-2466_2.patch, AMBARI-2466_branch-1.2.4_2.patch,
> AMBARI-2466_branch-1.2.4.patch, AMBARI-2466.patch,
> AMBARI-2466_upgrade_path.patch
>
>
> Ran into issues setting up Hive and Oozie with an Oracle database.
> 1. We are hard-coding port 1521 for the JDBC URL.
> 2. There are two types of JDBC URLs for Oracle:
> * jdbc:oracle:thin:@[HOST][:PORT]:SID
> * jdbc:oracle:thin:@//[HOST][:PORT]/SERVICE
> We are making the assumption that it is the latter, but this may not work
> depending on how Oracle is set up.
> 3. We prompt for the "Database Name". In Oracle context, this could be the
> SID or SERVICE NAME, but it's not clear what this is.
> As a solution to all of the above, we will construct the JDBC URL based on
> the database type, host, and name for Hive/Oozie and present it to the user
> as an editable text field during install.
> Post-install, the JDBC URL remains editable, but does not change
> automatically as changes other database-related parameters.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
