lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SOLR-812) JDBC optimizations: setReadOnly, setMaxRows
Date Sat, 13 Dec 2008 17:27:44 GMT

     [ https://issues.apache.org/jira/browse/SOLR-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shalin Shekhar Mangar updated SOLR-812:
---------------------------------------

    Attachment: SOLR-812.patch

Fixing a bug with the way maxRows is calculated. It was not being set if 'rows' is specified
but 'start' is not.

> JDBC optimizations: setReadOnly, setMaxRows
> -------------------------------------------
>
>                 Key: SOLR-812
>                 URL: https://issues.apache.org/jira/browse/SOLR-812
>             Project: Solr
>          Issue Type: Improvement
>          Components: contrib - DataImportHandler
>    Affects Versions: 1.3
>            Reporter: David Smiley
>         Attachments: SOLR-812.patch, SOLR-812.patch
>
>
> I'm looking at the DataImport code as of Solr v1.3 and using it with Postgres and very
large data sets and there some improvement suggestions I have.
> 1. call setReadOnly(true) on the connection.  DIH doesn't change the data so this is
obvious.
> 2. call setAutoCommit(false) on the connection.   (this is needed by Postgres to ensure
that the fetchSize hint actually works)
> 3. call setMaxRows(X) on the statement which is to be used when the dataimport.jsp debugger
is only grabbing X rows.  fetchSize is just a hint and alone it isn't sufficient.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message