[
https://issues.apache.org/jira/browse/SOLR-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648673#action_12648673
]
Glen Newton commented on SOLR-812:
----------------------------------
You might also think about setting
setTransactionIsolation(Connection.TRANSACTION_READ_UNCOMMITTED)
(see:
http://media.datadirect.com/download/docs/ddxquery/allddxq/reference/wwhelp/wwhimpl/common/html/wwhelp.htm?context=Reference&file=grammarwrite7.html)
Only DB2 appears to support TRANSACTION_NONE
--
While from the previous comment JdbcDataSource it appears not to exclusively be
a "source", you should still consider also setting:
setHoldability(ResultSet.CLOSE_CURSORS_AT_COMMIT)
It may reduce the driver resource usage.
Certainly exposing these and the above in JdbcDataSource via properties would
be more flexible to users. But sensible defaults should be set for read-only.
> 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
>
> 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.
