lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SOLR-1366) UnsupportedOperationException may be thrown when using custom IndexReader
Date Tue, 22 Sep 2009 13:38:16 GMT

     [ https://issues.apache.org/jira/browse/SOLR-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shalin Shekhar Mangar updated SOLR-1366:
----------------------------------------

    Attachment: SOLR-1366.patch

How about this?

{code}
** Experimental Feature **
Please note - Using a custom IndexReaderFactory may prevent certain other features
from working. The API to IndexReaderFactory may change without warning or may even
be removed from future releases if the problems cannot be resolved.

** Features that may not work with custom IndexReaderFactory **
The ReplicationHandler assumes a disk-resident index. Using a custom
IndexReader implementation may cause incompatibility between ReplicationHandler and
may cause replication to not work correctly. See SOLR-1366 for details.
{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: replication (java), search
>    Affects Versions: 1.4
>            Reporter: Andrzej Bialecki 
>            Assignee: Mark Miller
>             Fix For: 1.4
>
>         Attachments: searcher.patch, SOLR-1366.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.


Mime
View raw message