[
https://issues.apache.org/jira/browse/SOLR-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598664#action_12598664
]
patrick o'leary commented on SOLR-565:
--------------------------------------
There's one change I was going to add to this today which was a copy parameter,
I'll add that and look at some of the ideas here.
Here's what I suggest.
1) Add the change I've got, just to have a base line to work from.
2) Add changes into ShardRequest and SearchHandler (Maybe even response
builder) and this patch to handle essentially "named nodes" ?
- with parameters
3) Add an optional interface to provide intelligent query routing
- If not null, pass the response builder to the query routing class, and it
should pass a list of named nodes back that can be used
for the request.
Before anyone asks, I do no believe that this component should be responsible
for reformatting the query for each of the named nodes (which is open for
renaming if someone has something cooler to call it), the individual nodes
should be capable of taking user / client input and restructuring it to suit it
own needs.
> Component to abstract shards from clients
> -----------------------------------------
>
> Key: SOLR-565
> URL: https://issues.apache.org/jira/browse/SOLR-565
> Project: Solr
> Issue Type: New Feature
> Components: search
> Affects Versions: 1.3
> Reporter: patrick o'leary
> Priority: Minor
> Attachments: distributor_component.patch
>
>
> A component that will remove the need for calling clients to provide the
> shards parameter for
> a distributed search.
> As systems grow, it's better to manage shards with in solr, rather than
> managing each client.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
