[
https://issues.apache.org/jira/browse/LUCENE-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777162#action_12777162
]
Mark Miller edited comment on LUCENE-1558 at 11/12/09 8:26 PM:
---------------------------------------------------------------
Ah - didn't see this issue and assumed Uwe's change was what we were going with
so I updated the javadoc to reflect. If we change again, it will need another
tweak (adding back that its the current default).
*edit*
Personally, I'm not so sure its a bad idea making the user specify as it is now
- its not much work and will likely head off users wondering why they can't do
a write operation after making an IndexReader and not thinking about the param
or that its readonly.
was (Author: markrmil...@gmail.com):
Ah - didn't see this issue and assumed Uwe's change was what we were going
with so I updated the javadoc to reflect. If we change again, it will need
another tweak (adding back that its the current default).
> Make IndexReader/Searcher ctors readOnly=true by default
> --------------------------------------------------------
>
> Key: LUCENE-1558
> URL: https://issues.apache.org/jira/browse/LUCENE-1558
> Project: Lucene - Java
> Issue Type: Improvement
> Affects Versions: 2.4.1
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 3.0
>
>
> Another "change the defaults" in 3.0.
> Right now you get a read/write reader from IndexReader.open and new
> IndexSearcher(...), and reserving the right to write causes thread contention
> (on isDeleted).
> In 3.0 let's make readOnly reader the default, but still allow opening a
> read/write IndexReader.
--
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-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
