Dear Wiki user, You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.
The "SolrCloud" page has been changed by YonikSeeley. The comment on this change is: detail thoughts on querying specific slices / logical shards. http://wiki.apache.org/solr/SolrCloud?action=diff&rev1=14&rev2=15 -------------------------------------------------- http://localhost:8983/solr/collection1/select?collection=collection1_NY,collection1_NJ,collection1_CT&shards=auto }}} + === Querying Specific Shards === + This is brainstorming only - the terminology for shard/logical shard/shard id/slice has not been finalized. + Query specific slices (logical pieces, a subset of the whole index). In this example, the user has partitioned the index by date, creating a new slice (with corresponding shards) every month. {{{ http://localhost:8983/solr/collection1/select?shards=auto&slice=slice_200812,slice_200912,slice_201001 }}} + + The presence of "shards" is what currently signals that a request is distributed, and distrib search removes this param for sub-requests. + But with future micro-sharding or having a single core support multiple shards, the request will need to contain what shards are being requested. Reusing "shards" for this would require that either + a) The search component detect when it has all of the shards requested, and turn it into a non-distributed request (any error here could easily result in an infinite request loop until deadlock). It seems better to return a specific error if this node no longer contains the shard being queried in a non-distrib search. + b) Use a different distrib=true flag to indicate if this is a distributed search. This isn't back compatible though? Unless we also consider any request where shards contains a url to be distributed. + + {{{ + http://localhost:8983/solr/collection1/select?shards=shard_200812,shard_200912,shard_201001&distrib=true + }}} + = Developer Section = == TODO ==
