You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2009/05/24 18:29:45 UTC
[jira] Resolved: (LUCENE-1659) Make readOnly setting to
IndexReader.open / IndexSearcher ctor explicit
[ https://issues.apache.org/jira/browse/LUCENE-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael McCandless resolved LUCENE-1659.
----------------------------------------
Resolution: Duplicate
Losing my mind... dup of LUCENE-1657.
> Make readOnly setting to IndexReader.open / IndexSearcher ctor explicit
> -----------------------------------------------------------------------
>
> Key: LUCENE-1659
> URL: https://issues.apache.org/jira/browse/LUCENE-1659
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 2.9
>
>
> Most apps don't need writable IndexReader, and, a readOnly IndexReader
> has better concurrent performance.
> I'd love to simply default readOnly to true, and you'd have to specify
> "false" if you want a read/write reader (I think that's the natural
> default), but that'd likely break too many back-compat cases.
> So the workaround is to make the parameter explicit, in 2.9.
> I think even for IndexSearcher's methods that open an IndexReader
> under the hood, we should also make the parameter explicit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org