Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
Message-ID: <1319013287.1252533598028.JavaMail.jira@brutus>
Date: Wed, 9 Sep 2009 14:59:58 -0700 (PDT)
From: "Andrzej Bialecki  (JIRA)" <jira@apache.org>
To: solr-dev@lucene.apache.org
Subject: [jira] Commented: (SOLR-1366) UnsupportedOperationException may be
 thrown when using custom IndexReader
In-Reply-To: <616531992.1250591774943.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SOLR-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753289#action_12753289 ] 

Andrzej Bialecki  commented on SOLR-1366:
-----------------------------------------

FYI, for now I solved this by extending my IndexReader to support this call and return the original directory that lists all index files plus a few resources that I care about. However, this is just glossing over the deeper problem - replication handler shouldn't assume the directory is file-based.

> 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.