Return-Path: X-Original-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C5BB410AD2 for ; Sat, 22 Jun 2013 00:29:20 +0000 (UTC) Received: (qmail 82402 invoked by uid 500); 22 Jun 2013 00:29:20 -0000 Delivered-To: apmail-incubator-ambari-dev-archive@incubator.apache.org Received: (qmail 82353 invoked by uid 500); 22 Jun 2013 00:29:20 -0000 Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ambari-dev@incubator.apache.org Delivered-To: mailing list ambari-dev@incubator.apache.org Received: (qmail 82344 invoked by uid 99); 22 Jun 2013 00:29:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Jun 2013 00:29:20 +0000 Date: Sat, 22 Jun 2013 00:29:20 +0000 (UTC) From: "Yusaku Sako (JIRA)" To: ambari-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-2466) Hive/Oozie database settings should accept custom JDBC URLs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690946#comment-13690946 ] Yusaku Sako commented on AMBARI-2466: ------------------------------------- Actually, I just realized that I did not test the upgrade paths right (was testing without the patch :) Getting errors when Saving Oozie and Hive configs after upgrade. Please do not commit this yet. > 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 > > > 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