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

Alexandre Rafalovitch closed SOLR-255.
--------------------------------------

Resolved long time ago, but was not "closed".

> RemoteSearchable for Solr(use RMI)
> ----------------------------------
>
>                 Key: SOLR-255
>                 URL: https://issues.apache.org/jira/browse/SOLR-255
>             Project: Solr
>          Issue Type: Improvement
>          Components: search
>            Reporter: Toru Matsuzawa
>            Assignee: Otis Gospodnetic
>            Priority: Major
>         Attachments: solr-multi20070606.zip, solr-multi20070724..zip
>
>
> I experimentally implemented RemoteSearchable of Lucene for Solr.
> I referred to "FederatedSearch" and used RMI. 
> Two or more Searchers can be referred to with SolrIndexSearcher.
> These query-only indexes can be specified in solrconfig.xml, 
> enumerating the list under a <searchIndex> tag.
>   <searchIndex>
>     <lst>E:\sample\data1</lst>
>     <lst>E:\sample\data2</lst>
>     <lst>rmi://localhost</lst>
>   </searchIndex>
> The index in the dataDir is also used as the default index of solr
> to update and query.
> When data of a document in a index specified under the <searchIndex> is
> updated, 
> that document data in the index will be deleted and data of the updated 
> document will be stored
> in the index in the dataDir.
> SolrRemoteSearchable (the searcher for remote access) is started from 
> SolrCore 
> by specifying "< remoteSearcher>true</remoteSearcher >" in solrconfig.xml.(It 
> is registered in RMI. )
> ("-Djava.security.policy" should be set when you start VM. )
> Not all of the operational cases are tested 
> because Solr has so many features. 
> Moreover, TestUnit has not been made 
> because I made this through a trial and error process. 
> Some changes are required in Lucene to execute this. 
> I need your comments on this although it might be hard without TestUnit. 
> I especially worry about the followings: 
> - Am I on the right truck about this issue?
> - Is the extent of modifying Lucene tolerable?
> - Are there any ideas to implement this feature without modifying Lucene?
> - Does this idea contribute for improving Solr?
> - This implementation may partially overlap with "Multiple Solr Cores".
>   What should be done?
> - Are there any other considerations about this issue, which I have 
> overlooked?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to