[
https://issues.apache.org/jira/browse/SOLR-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046144#comment-13046144
]
Yonik Seeley commented on SOLR-705:
-----------------------------------
Something to keep in mind is the difference between logical shard and physical
shard replica.
i.e. "shard1" can be located at localhost:8983/solr/shard1 and
localhost:7574/solr/shard1
Both pieces of info can be useful.
So with ryan's last commit, [shard] gets you something like
localhost:8983/solr/shard1
We don't have to implement returning the other part now... but we should think
about the naming.
In the code, I sometimes used "slice" to mean logical shard (a logical slice of
the complete index), to avoid overloading "shard"... but I'm not sure that
won't cause more confusion than it's worth. So for a future logical shard
name, perhaps [shard_id] ?
> Distributed search should optionally return docID->shard map
> ------------------------------------------------------------
>
> Key: SOLR-705
> URL: https://issues.apache.org/jira/browse/SOLR-705
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.3
> Environment: all
> Reporter: Brian Whitman
> Assignee: Ryan McKinley
> Fix For: 4.0
>
> Attachments: SOLR-705.patch, SOLR-705.patch, SOLR-705.patch,
> SOLR-705.patch, SOLR-705.patch, SOLR-705.patch
>
>
> SOLR-303 queries with &shards parameters set need to return the dociD->shard
> mapping in the response. Without it, updating/deleting documents when the #
> of shards is variable is hard. We currently set this with a special
> requestHandler that filters /update and inserts the shard as a field in the
> index but it would be better if the shard location came back in the query
> response outside of the index.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
