Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Message-ID: <307108765.1257473852392.JavaMail.jira@brutus>
Date: Fri, 6 Nov 2009 02:17:32 +0000 (UTC)
From: "Joey Surls (JIRA)" <jira@apache.org>
To: java-dev@lucene.apache.org
Subject: [jira] Commented: (LUCENE-2036) Underlying Spatial Logic does not
 work in Remote Settings
In-Reply-To: <122499290.1257456212543.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/LUCENE-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774187#action_12774187 ] 

Joey Surls commented on LUCENE-2036:
------------------------------------

This is unfortunate.

The use case is the following: I am working with a large index that doesn't fit on a single machine. I can split it into multiple indexes on various machines. I can then use ParallelMultiSearcher to query across the indexes and aggregate the results. Making this a remote ParallelMultiSearcher is pretty trivial b/c of the well designed Lucene APIs.

I do not want to have to go back and change code to be aware of the remote protocol. Instead I should be able to implement a Searcher that has some smarts built in it to know how to find the right remote Searcher to query. Then b/c of inversion of control I could then swap out the remote searcher with the local one in my spring app context xml.


Is there any idea as to when the spatial code is going to be rewritten?

> Underlying Spatial Logic does not work in Remote Settings
> ---------------------------------------------------------
>
>                 Key: LUCENE-2036
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2036
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: contrib/spatial
>    Affects Versions: 2.9
>            Reporter: Joey Surls
>         Attachments: LuceneSpatialTest.java
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> I am using Lucene in a distributed setup.
> I have a remote Searcher on another machine executing the methods in Searcher. For regular text searches I have no problem. For the Spatial contrib (according to examples provided) there is underlying logic that is lost when the Filter and Sort get serialized. I've attached a junit test case that shows when I mimic Java RMI (by serializing the objects and read it back) I get a null pointer exception. I believe it has to do with the Sort (or Filter) referencing objects in the other  class Filter (or Sort)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org