Return-Path: 
 <solr-dev-return-20146-apmail-lucene-solr-dev-archive=lucene.apache.org@lucene.apache.org>
Delivered-To: apmail-lucene-solr-dev-archive@minotaur.apache.org
Received: (qmail 77021 invoked from network); 22 Sep 2009 09:02:42 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 22 Sep 2009 09:02:42 -0000
Received: (qmail 38143 invoked by uid 500); 22 Sep 2009 09:02:39 -0000
Delivered-To: apmail-lucene-solr-dev-archive@lucene.apache.org
Received: (qmail 38053 invoked by uid 500); 22 Sep 2009 09:02:39 -0000
Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:solr-dev-help@lucene.apache.org>
List-Unsubscribe: <mailto:solr-dev-unsubscribe@lucene.apache.org>
List-Post: <mailto:solr-dev@lucene.apache.org>
List-Id: <solr-dev.lucene.apache.org>
Reply-To: solr-dev@lucene.apache.org
Delivered-To: mailing list solr-dev@lucene.apache.org
Received: (qmail 38034 invoked by uid 99); 22 Sep 2009 09:02:39 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Sep 2009 09:02:39 +0000
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 shalinmangar@gmail.com
 designates 209.85.221.181 as permitted sender)
Received: from [209.85.221.181] (HELO mail-qy0-f181.google.com)
 (209.85.221.181)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Sep 2009 09:02:30 +0000
Received: by qyk11 with SMTP id 11so11500qyk.20
        for <multiple recipients>; Tue, 22 Sep 2009 02:02:09 -0700 (PDT)
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:cc:content-type;
        bh=WW+itr9mygxFgEWurjdTu6Aee3FlFMAruA9KznPeTeE=;
        b=lWvQpHOADEimjuahV9/lipOA0f6mIy/LXRmxOuyjT+It8O7Iohf1rwJA3Gr1SZnYxE
         Q1iyiJA12r66SHYZ7a8Aw/T9XSZW8YLmR2licnNeGYLTveyiq8tJhCUX0cC0DvHM2Ble
         HRE213IewoAs9lYEJ7jZFMryp+No20XnT5jgU=
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
         :cc:content-type;
        b=no0idgE1BENtmJRQdQ/hfJYZjthyuKR6YLjQmvxXereVg9EzvOWZHuD2+AEpPi94My
         2n9IoOD/yjM47rLRQzvc3MNRIEC746j5zWFIRuXy7TuEoW21XrP1n23HL0V7DRHmkAQ0
         CwIYLP45YPwOqa21IlZ57EuDe6GtrHlbrAnBE=
MIME-Version: 1.0
Received: by 10.229.102.85 with SMTP id f21mr171111qco.42.1253610129025; Tue,
	22 Sep 2009 02:02:09 -0700 (PDT)
In-Reply-To: <a426e5000909220159k4ba0f905q70c9be2350a33927@mail.gmail.com>
References: <a426e5000909220159k4ba0f905q70c9be2350a33927@mail.gmail.com>
Date: Tue, 22 Sep 2009 14:32:08 +0530
Message-ID: <69de18140909220202o60840625w295f6e34fcba5945@mail.gmail.com>
Subject: Re: DIH import "out of memory" problem (batchSize and autoCommit not
	working)
From: Shalin Shekhar Mangar <shalinmangar@gmail.com>
To: solr-dev@lucene.apache.org
Cc: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=002354471a206d6c93047426daaa
X-Virus-Checked: Checked by ClamAV on apache.org

--002354471a206d6c93047426daaa
Content-Type: text/plain; charset=UTF-8

On Tue, Sep 22, 2009 at 2:29 PM, Steve Sun <steve@anobii.com> wrote:

> Hi,
>
> I spent a whole day trying to make "batchSize" work for JdbcDataSource with
> "org.postgresql.Driver", but got frustrated.  At last I took a look into
> DIH's source code and found that there's actually a bug in there.  When JDBC
> driver is placed in <solr-home>/lib (as instructed by DIHQuickStart page of
> Solr wiki), but not in tomcat's lib directory, the JDBC connection will not
> be configured as specified in the DIH configuration at all.  Attributes like
> autoCommit, readOnly and batchSize will be ignored.  The fix is simple, have
> attached my patch.
> (contrib/dataimporthandler/src/main/java/org/apache/solr/handler/dataimport/JdbcDataSource.java
> r817524)
>
> One work-around is: place your JDBC driver jar under tomcat's application
> lib directory.  e.g., tomcat/webapps/solr/WEB-INF/lib/
>
> Have only tested with postgresql drivers, but seems the problem is generic
> to all drivers placed in <solr-home>/lib.
>

Thanks Steve. The mailing list removed your attachment. Can you please open
a jira issue and attach a patch there?

-- 
Regards,
Shalin Shekhar Mangar.

--002354471a206d6c93047426daaa--