[
https://issues.apache.org/jira/browse/SOLR-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744542#action_12744542
]
Mark Miller commented on SOLR-1366:
-----------------------------------
bq. This call is used only to retrieve the full path of the directory for
informational purpose, so it shouldn't lead to a crash.
The replication handler uses it a lot (assuming its a file) - I almost feel we
should add some javadoc about how using non FSDirectory based IndexReaders is
supported. I'm not even fully sure myself.
Also, are we positive it behaves here correctly in SolrCore ?
{code}
File indexDirFile = new File(getIndexDir()).getCanonicalFile();
File newIndexDirFile = new File(newIndexDir).getCanonicalFile();
if (newestSearcher != null && solrConfig.reopenReaders
&& indexDirFile.equals(newIndexDirFile)) {
{code}
> 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: 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.
