Return-Path: Delivered-To: apmail-hadoop-core-user-archive@www.apache.org Received: (qmail 40030 invoked from network); 4 Feb 2009 18:27:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Feb 2009 18:27:02 -0000 Received: (qmail 48173 invoked by uid 500); 4 Feb 2009 18:26:56 -0000 Delivered-To: apmail-hadoop-core-user-archive@hadoop.apache.org Received: (qmail 48012 invoked by uid 500); 4 Feb 2009 18:26:55 -0000 Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-user@hadoop.apache.org Delivered-To: mailing list core-user@hadoop.apache.org Received: (qmail 48001 invoked by uid 99); 4 Feb 2009 18:26:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Feb 2009 10:26:55 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of amansk@gmail.com designates 74.125.92.25 as permitted sender) Received: from [74.125.92.25] (HELO qw-out-2122.google.com) (74.125.92.25) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Feb 2009 18:26:47 +0000 Received: by qw-out-2122.google.com with SMTP id 3so699384qwe.35 for ; Wed, 04 Feb 2009 10:26:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=qzIysh6M3EX2iYBG/IGa/w3AYjoAEynZFZsjMhHx50s=; b=TND+doTW0k6rkIDBf3caFMPRmDDvKaeBcWPlGB3XBwUTu0KLQeRMZ/YeHtN9kamjEM 7N6ZGagDplVjr+1CIfl6bzWpI5n+nQ5VYNmX1m3A0iYCB0GFLWSpjHgUVMhDUs/PyZEK EM7XGpLjJsl2BOrb8RiBNBTOPd+sVDx/HTQPg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=hV1OUCiBYVEZoBBbXZm4MIm7P3ooHeclZNXD0jzbQlqe0PuVFmCTPGsj2MTVtareRV MQuCNLyyoK84tTU7GLfHCxYCDB1hLeclS28XeIRCNlrxSBmPhRZOji0tII18lbrmMAGs zc1pavpNr1jfelbZ8PPIZUcanQ9MVsRPNLCPA= MIME-Version: 1.0 Received: by 10.215.66.9 with SMTP id t9mr10943759qak.214.1233771986224; Wed, 04 Feb 2009 10:26:26 -0800 (PST) In-Reply-To: <4989B09C.7000207@gmail.com> References: <35a22e220902031817s30eb8426y2b6e273470966b9a@mail.gmail.com> <4989B09C.7000207@gmail.com> Date: Wed, 4 Feb 2009 10:26:26 -0800 Message-ID: <35a22e220902041026pbdcc2f6q2a447b94daf3daa2@mail.gmail.com> Subject: Re: HADOOP-2536 supports Oracle too? From: Amandeep Khurana To: core-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=0015175cf7eef907de04621bec5d X-Virus-Checked: Checked by ClamAV on apache.org --0015175cf7eef907de04621bec5d Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Ok. I'm not sure if I got it correct. Are you saying, I should test the statement that hadoop creates directly with the database? Amandeep Amandeep Khurana Computer Science Graduate Student University of California, Santa Cruz On Wed, Feb 4, 2009 at 7:13 AM, Enis Soztutar wrote: > Hadoop-2536 connects to the db via JDBC, so in theory it should work with > proper jdbc drivers. > It has been tested against MySQL, Hsqldb, and PostreSQL, but not Oracle. > > To answer your earlier question, the actual SQL statements might not be > recognized by Oracle, so I suggest the best way to test this is to insert > print statements, and run the actual SQL statements against Oracle to see if > the syntax is accepted. > > We would appreciate if you publish your results. > > Enis > > > Amandeep Khurana wrote: > >> Does the patch HADOOP-2536 support connecting to Oracle databases as well? >> Or is it just limited to MySQL? >> >> Amandeep >> >> >> Amandeep Khurana >> Computer Science Graduate Student >> University of California, Santa Cruz >> >> >> > --0015175cf7eef907de04621bec5d--