[
https://issues.apache.org/jira/browse/SOLR-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756652#action_12756652
]
Andrzej Bialecki commented on SOLR-1366:
-----------------------------------------
+1 for adding a big red flag. My application depends on this functionality, and
it's working well once I overrode a bunch of additional methods in IndexReader
that deal with Directory, IndexCommit, index version, etc.
(A few details on this, and why my solution is not applicable in general case:
I'm using ParallelReader, and the other indexes that I add are throwaways, i.e.
I recreate them on each index refresh from external shared resources. So I
basically short-circuited those methods that deal with directory and commits so
that they return information from the main index. This way the file-based
replication works as before for the main index).
> 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.
