[
https://issues.apache.org/jira/browse/SOLR-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702171#action_12702171
]
Mark Miller commented on SOLR-1088:
-----------------------------------
I think I added that method with the readonly patch - I figured it was a good
idea to allow a searcher of either type (you get a non readonly otherwise). I
don't know why it was commented out though (there really should be a comment
about that included). We should drop it or fix it for sure. I think it makes
sense to keep, and I'd just fix it, but I don't know why it was commented out
to begin with so...
> newSearcher(String name, boolean readOnly) is broken
> ----------------------------------------------------
>
> Key: SOLR-1088
> URL: https://issues.apache.org/jira/browse/SOLR-1088
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Fix For: 1.4
>
>
> Noted on the mailing list while investigating something semi-related, the
> method SolrCore.newSearcher(String name, boolean readOnly) doesn't work as
> advertised (the readOnly option is completely ignored)
> the method isn't used anywhere in Solr (that i could find) but it might be
> used by clients ... we should deal with this in some way prior to the 1.4
> release (either fix; fix & deprecate; or document problem and deprecate)
> http://www.nabble.com/Re%3A-Lucene-sync-bottleneck--p22237748.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
