On Thu, Jan 14, 2010 at 1:58 PM, Chris Hostetter <hossman_luc...@fucit.org> wrote: > : parameter we use for this. Suggestions? logicalshards=shard1,shard2? > : lshards=shard1,shard2? slice=shard1,shard2? It doesn't seem like it > : would be easy to reuse the "shards" parameter for this since it refers > : to physical shard addresses. > > I haven't been following the SolrCloud stuff much, but from a client > perspective is there really any difference between asking for a physical > shard, vs asking for a logical shard (or slice name)? ... shouldn't the > later case just result in a resolution from logical->physical w/o > requiring the client code to know/care wether the String they have is a > physical shard URL, or a slice name.
That might be doable... but we would need to be able to tell the difference. Perhaps we could always require a slash in a physical address (localhost/context) and prohibit it in slice names? But... I think there's still a potentially bigger difference: today, if shards is set, it means it's a distributed search (and shards is removed for sub-requests). But the slice of the index being requested may not have a one-to-one mapping with a full request on a solr core. And shards may be able to move around, and so it seems important to be able to declare what part of the index you're looking for when you're querying a shard. -Yonik http://www.lucidimagination.com
