Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 12926 invoked from network); 3 Nov 2008 22:33:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Nov 2008 22:33:07 -0000 Received: (qmail 40933 invoked by uid 500); 3 Nov 2008 22:33:13 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 40279 invoked by uid 500); 3 Nov 2008 22:33:11 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 40268 invoked by uid 99); 3 Nov 2008 22:33:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Nov 2008 14:33:11 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Nov 2008 22:32:02 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 57434234C26E for ; Mon, 3 Nov 2008 14:32:44 -0800 (PST) Message-ID: <505832394.1225751564356.JavaMail.jira@brutus> Date: Mon, 3 Nov 2008 14:32:44 -0800 (PST) From: "Prasad Chakka (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-4101) Support JDBC connections for interoperability between Hive and RDBMS In-Reply-To: <1443032500.1220802164192.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644835#action_12644835 ] Prasad Chakka commented on HADOOP-4101: --------------------------------------- Regarding unused files in metastore, these are the files that got carried over hive prototype which used file based metastore. We left them there in case some one wants to use file based metastore. So in a sense they are useful and there are tests. I think we should combine the servers now. It will be difficult and time consuming to merge them later. Advanced users can still have two installations of the same server but direct metadata calls to one server and data calls to another server. But the default case, there will be only one server and easier for maintenance. Only issue I see is that metastore code is independent of ql/cli code. So it might be better to build JDBC server on top of metastore server (ie extend metastore server) and import metastore thrift IDL into service thrift IDL. So the JDBC service would be a superset of metastore functionality. What do you guys think? > Support JDBC connections for interoperability between Hive and RDBMS > -------------------------------------------------------------------- > > Key: HADOOP-4101 > URL: https://issues.apache.org/jira/browse/HADOOP-4101 > Project: Hadoop Core > Issue Type: Improvement > Components: contrib/hive > Reporter: YoungWoo Kim > Priority: Minor > Attachments: hadoop-4101.1.patch > > > In many DW and BI systems, the data are stored in RDBMS for now such as oracle, mysql, postgresql ... for reporting, charting and etc. > It would be useful to be able to import data from RDBMS and export data to RDBMS using JDBC connections. > If Hive support JDBC connections, It wll be much easier to use 3rd party DW/BI tools. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.