: 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. This seems completley analogous to hostnames: - I'm an applciation. - via some means, i've got a (String) $host - I ask my networking library to open a connection to $host - the networking library worries about wether $host is a name or an IP - if $host is an alias, the DNS server resolves it to a hostname - if $host is a hostname, the DNS server resolves it to an IP (possibly round robin) Likewise in Solr: - I'm an applciation. - via some means, i've got a (Set<String>) $shards - I ask Solr to search across $shards - Solr looks at each item in $shards - if it's the name of a slice, it picks a physical shard - if it's a physical shard, it uses that shard ...there's got to be a mapping from slice_name=>Set(physical_shards) anyway right? why should the client have to know the difference? -Hoss
