Return-Path: Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: (qmail 2956 invoked from network); 7 Jul 2009 13:30:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 7 Jul 2009 13:30:29 -0000 Received: (qmail 22842 invoked by uid 500); 7 Jul 2009 13:30:39 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 22807 invoked by uid 500); 7 Jul 2009 13:30:39 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 22797 invoked by uid 99); 7 Jul 2009 13:30:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jul 2009 13:30:39 +0000 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; Tue, 07 Jul 2009 13:30:36 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 44694234C004 for ; Tue, 7 Jul 2009 06:30:15 -0700 (PDT) Message-ID: <480519182.1246973415265.JavaMail.jira@brutus> Date: Tue, 7 Jul 2009 06:30:15 -0700 (PDT) From: "Hadoop QA (JIRA)" To: mapreduce-issues@hadoop.apache.org Subject: [jira] Commented: (MAPREDUCE-716) org.apache.hadoop.mapred.lib.db.DBInputformat not working with oracle MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/MAPREDUCE-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728092#action_12728092 ] Hadoop QA commented on MAPREDUCE-716: ------------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12412687/HADOOP-5482.trunk.patch against trunk revision 791739. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. -1 contrib tests. The patch failed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/361/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/361/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/361/artifact/trunk/build/test/checkstyle-errors.html Console output: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/361/console This message is automatically generated. > org.apache.hadoop.mapred.lib.db.DBInputformat not working with oracle > --------------------------------------------------------------------- > > Key: MAPREDUCE-716 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-716 > Project: Hadoop Map/Reduce > Issue Type: Bug > Environment: Java 1.6, HAdoop0.19.0, Linux..Oracle, > Reporter: evanand > Attachments: HADOOP-5482.20-branch.patch, HADOOP-5482.patch, HADOOP-5482.trunk.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > org.apache.hadoop.mapred.lib.db.DBInputformat not working with oracle. > The out of the box implementation of the Hadoop is working properly with mysql/hsqldb, but NOT with oracle. > Reason is DBInputformat is implemented with mysql/hsqldb specific query constructs like "LIMIT", "OFFSET". > FIX: > building a database provider specific logic based on the database providername (which we can get using connection). > I HAVE ALREADY IMPLEMENTED IT FOR ORACLE...READY TO CHECK_IN CODE -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.