Created: (SOLR-255) RemoteSearchable for Solr(use RMI)

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


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:sampledata1</lst>
    <lst>E:sampledata2</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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.

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

Toru Matsuzawa updated SOLR-255:
--------------------------------

    Attachment: solr-multi20070606.zip

I attached the patch for Lucene, the patch for Solr 
and solrconfig.xml to execute this.

My response could be very slow because of my poor English
ability. 

> 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
>         Attachments: solr-multi20070606.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:sampledata1</lst>
>     <lst>E:sampledata2</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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.

    [ https://issues.apache.org/jira/browse/SO
LR-255?page=com.atlassian.jira.plugin.system.issuetabpanels:
comment-tabpanel#action_12504740 ] 

Otis Gospodnetic commented on SOLR-255:
---------------------------------------

I took only a very quick look at this and noticed changes
are done in Lucene.  Any such changes should be brought up
on the java-devlucene.... mailing list and posted as a
patch in Lucene's JIRA.  You can explain why you need to
make those changes.

I didn't take a closer look at your Solr changes, but from
your description above, my guess is that this will clash, at
least somewhat, with SOLR-215.

Is this what you implemented?
                                                   remote
lucene index (not Solr?)
                                                  /
                                               RMI
client -----> solr instance /
                                             
                                               RMI
                                                  
                                                   remote
lucene index (not Solr?)

Thanks.

> 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
>         Attachments: solr-multi20070606.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:sampledata1</lst>
>     <lst>E:sampledata2</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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.

    [ https://issues.apache.org/jira/browse/SO
LR-255?page=com.atlassian.jira.plugin.system.issuetabpanels:
comment-tabpanel#action_12505078 ] 

Toru Matsuzawa commented on SOLR-255:
-------------------------------------

My implementation is as follows.

client --> Solr instance  +/data/index
                                          
+/local/other/solr1/data/index
                                          
+/local/other/solr2/data/index
                                          
+/local/other/solr3/data/index
                                            |
                                           +--- RMI <---
Remote Solr index(/data/index)
                                            |
                                           +--- RMI <---
Remote Solr index(/data/index)

First of all, I'd like to get your comments whether my
modification is beneficial for Solr.
If it is helpful, is it possible to implement this changes
without modifying Lucene? 
I need your comments on this point.(If you have any other
ideas for the implementation, please let me know.)

After it becomes clear the necessity of modifying Lucene,
I'd like to post it to Lucene's JIRA.

I understand there are some overlaps with SOLR-215.
However, I think this modification can coexist with
SOLR-215.

Thank you.



> 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
>         Attachments: solr-multi20070606.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:sampledata1</lst>
>     <lst>E:sampledata2</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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.

    [ https://issues.apache.org/jira/browse/SO
LR-255?page=com.atlassian.jira.plugin.system.issuetabpanels:
comment-tabpanel#action_12507326 ] 

Henri Biestro commented on SOLR-255:
------------------------------------

Toru,
I've been looking quickly at your patch and kinda
understands why Otis is pushing for a merge. 
I dont know how this is usually done; should we merge the 2
issues and merge our patches?
I can try & see how this goes if you want.

One thing that worries me though is the Lucene patch
dependency; any way to only have a Solr patch?
I would suspect that Lucene committers are as busy as Solr
's so the review process might take sometime.
Although from far, it does look like pretty harmless changes
so there is hope...

As a side note, I was wondering if we could extend you
patch's functionality and get read/write capability per
index (as in http://hellonline.co
m/blog/?p=55 ,document indexing load balancing could be
performed on hashing unique key % number of indexes for
instance or by some configurable class). The current
functionality would be retained by specificying 'read-only'
versus 'read-write' for each index.

Nice job btw.
Henri


> 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
>         Attachments: solr-multi20070606.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:sampledata1</lst>
>     <lst>E:sampledata2</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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.

    [ https://issues.apache.org/jira/browse/SO
LR-255?page=com.atlassian.jira.plugin.system.issuetabpanels:
comment-tabpanel#action_12508380 ] 

Toru Matsuzawa commented on SOLR-255:
-------------------------------------

Hi Otis & Henri,

Otis Gospodnetic wrote:
> So with your patch one can search any *one* of those
indices,
> or any *group* of those indices, 
> correct?  In the case where a *group* of indices is
searched,
> do you search them in parallel and merge the results?

With my patch one can search a group of these indeces.
Each index in the group is searched in sequence, 
and then each result is merged.

Henri Biestro wrote:
> I've been looking quickly at your patch and 
> kinda understands why Otis is pushing for a merge. 
> I dont know how this is usually done; 
> should we merge the 2 issues and merge our patches?
> I can try & see how this goes if you want.

I inspected the patch of SOLR-215. 
The overlaps between SOLR-215 and SOLR255 are 
in the constructor of SolrIndexSearcher and SolrCore.
Each modification should be committed sequentially.
After that, there are not many additional modifications.

The commitment should be done through some stages. 
(It might be acceptable Step1 and Step2 is in reverse order.
Or, simultaneous? ) 
Step1) MultiCore (SOLR-215) 
Step2) The functionality of MultiSearcher, exclude
modification of RMI and Lucene.
       (SolrMultiSearcher and SolrIndexSearchable) 
Step3) The modification of Lucene
Step4) The functional addition to the RMI
(SolrRemoteSearcher) 
       (When it becomes MultiCore, additional modification,
in which 
        the remote object of RMI should be created
dynamically, will be needed.)

> One thing that worries me though is the Lucene patch
dependency; 
> any way to only have a Solr patch?
> I would suspect that Lucene committers are as busy as
Solr 's 
> so the review process might take sometime.
> Although from far, it does look like pretty harmless
changes so there is hope...

The RMI (SolrRemoteSearcher) causes the Lucene patch
dependency.
There will be no impact on SOLR-215 by the above-mentioned
procedure.

> As a side note, I was wondering if we could extend 
> you patch's functionality and get read/write capability
per index
> (as in http://hellonline.co
m/blog/?p=55 ,
> document indexing load balancing could be performed 
> on hashing unique key % number of indexes for instance

> or by some configurable class). 
> The current functionality would be retained 
> by specificying 'read-only' versus 'read-write' for
each index.

I also have ideas about this but those are not concrete
enough.
Anyway, that will be done through Step5 and later.

Thanks.


> 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
>         Attachments: solr-multi20070606.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:sampledata1</lst>
>     <lst>E:sampledata2</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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.

    [ https://issues.apache.org/jira/browse/SO
LR-255?page=com.atlassian.jira.plugin.system.issuetabpanels:
comment-tabpanel#action_12508385 ] 

Yonik Seeley commented on SOLR-255:
-----------------------------------

Toru, could you give an overview of how this solution works,
what data is passed over the network, and how well you think
it scales?  What is done on the shards, and what is done on
the "combiner" to sort hits by a certain field? 
to facet by a certain field?  Some of the methods on
SolrSearchable make me nervous about scalability (like
getInts(field), getFloats(field)) but it's not easy to tell
if/when those are used.



> 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
>         Attachments: solr-multi20070606.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:sampledata1</lst>
>     <lst>E:sampledata2</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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.

    [ https://issues.apache.org/jira/browse/SO
LR-255?page=com.atlassian.jira.plugin.system.issuetabpanels:
comment-tabpanel#action_12508394 ] 

Yonik Seeley commented on SOLR-255:
-----------------------------------

A few other considerations for good scalability:
 - shards should be searched in parallel
 - there needs to be multiple copies of each shard (esp for
HA), with failover, otherwise splitting and distributing the
index will lead to higher failure rates.


> 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
>         Attachments: solr-multi20070606.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:sampledata1</lst>
>     <lst>E:sampledata2</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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.

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

Toru Matsuzawa updated SOLR-255:
--------------------------------

    Attachment: solr-multi20070724..zip

Pache Updated.

The following changes.
1) Addition of easy TestUnit.
2) search for shards in parallel.
3) Cash(like FieldCache) is added to
getInts(filed),getStringIndex(filed) etc.
4) Bug fix of "sort asc".

Standalone/solr-multi20070724-NoRMI.patch is a patch for
local index searches only.
Please use the patch of RMI/lucene4solr-multi.patch and
RMI/solr-multi20070724.patch when you use RMI. 
(lucene4solr-multi.patch is patch for lucene. )


> 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
>         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:sampledata1</lst>
>     <lst>E:sampledata2</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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.

    [ https://issues.apache.org/jira/browse/SO
LR-255?page=com.atlassian.jira.plugin.system.issuetabpanels:
comment-tabpanel#action_12516107 ] 

Stu Hood commented on SOLR-255:
-------------------------------

Everyone working on this patch should check out
http://lucene.zones.apache.org:8080/hudson/job/Luce
ne-Nightly/javadoc/org/apache/lucene/search/ParallelMultiSea
rcher.html
and make sure no work is being duplicated. My company is
using 'ParallelMultiSearcher' in a production environment
with great success, so I wanted to make it is on everyone's
radar.

Thanks!

> 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
>         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:sampledata1</lst>
>     <lst>E:sampledata2</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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.