[
https://issues.apache.org/jira/browse/SOLR-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745042#action_12745042
]
Shalin Shekhar Mangar commented on SOLR-1366:
---------------------------------------------
Yeah, ReplicationHandler assumes a file based IndexReader. We can document this
clearly.
{quote}
.. I haven't looked into it yet, but perhaps this could be solved by extending
the replication handler to support multiple dirs, and for those IndexReader
that don't support directory() try asking for getSubReaders() and use their
directory() ...
{quote}
Yes but that becomes complicated very fast. You'd need to know the correct
directory to which a newly downloaded file has to be written on the slave.
You'd also need to re-open readers selectively and you'd need to change their
directories (for cases where an existing file is to be deleted/replaced).
We anyway need to take a look at replication again after 1.4 with a focus on
Lucene's NRT capabilities.
> 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.
