[
https://issues.apache.org/jira/browse/SOLR-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753711#action_12753711
]
Yonik Seeley commented on SOLR-1366:
------------------------------------
bq. So, it seems for 1.4 we could fix this problem
What's the fix/workaround though? Solr currently assumes a disk resident
index, and the patch here makes up a directory... that doesn't seem like a good
idea. It also seems too late in the release cycle to try and abstract away
from a disk index... potentially complex and invasive.
> 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.
