[
https://issues.apache.org/jira/browse/SOLR-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756634#action_12756634
]
Hoss Man commented on SOLR-1366:
--------------------------------
The core issue here seems to stem from incompatible assumptions between various
pieces of code in Solr, and the new IndexReaderFactory functionality introduced
in 1.4 by SOLR-243.
If we don't have a silver bullet for solving all the discrepancies before 1.4,
then the safest approach seems to be making sure the documentation (and example
configs) for IndexReaderFactory have big flashing red "Experimental!"
disclaimers on them warning that using an IndexReaderFactory prevents certain
other features from working (list all the ones we know about) and that the API
for IndexReaderFactory may change at anytime w/o warning or be removed from
future release if the problems can't be resolved.
I'm tempted to suggest we remove SOLR-243 altogether, but there are _some_ use
cases of it that can work well for people, so it would be a shame to gut it
completely.
> UnsupportedOperationException may be thrown when using custom IndexReader
> -------------------------------------------------------------------------
>
> Key: SOLR-1366
> URL: https://issues.apache.org/jira/browse/SOLR-1366
> Project: Solr
> Issue Type: Bug
> Components: replication (java), search
> Affects Versions: 1.4
> Reporter: Andrzej Bialecki
> Assignee: Mark Miller
> Fix For: 1.4
>
> Attachments: searcher.patch
>
>
> If a custom IndexReaderFactory is specifiedd in solrconfig.xml, and
> IndexReader-s that it produces don't support IndexReader.directory() (such as
> is the case with ParallelReader or MultiReader) then an uncaught
> UnsupportedOperationException is thrown.
> This call is used only to retrieve the full path of the directory for
> informational purpose, so it shouldn't lead to a crash. Instead we could
> supply other available information about the reader (e.g. from its toString()
> method).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
