On Wed, Feb 10, 2010 at 12:02 AM, Jon Gifford <jon.giff...@gmail.com> wrote:
> Alternatively, I could create a collection per customer, which removes
> the need for slices, but means duplicating the schema many times.

Multiple collections should be able to share a single config (schema
and related config files).

[...]
> when a core is created, we should be able to specify
> the collection and slice that they belong to, via the REST interface.

Yep.

Note: I've backed off of the use of "slice" in the public APIs since
it was contentious (although I still think it's a useful concept and
it does remain in some of the code).  "shard" is kind of ambiguous,
but people are pretty good at dealing with ambiguity (and removing
that ambiguity by introducing another term seemed to add more
perceived complexity).

> The second part of what I need is to be able to search a single
> customers index, which I'm assuming will be a slice. Something like:
>
>    http://localhost:8983/solr/collection1/select?distrib=true&slice=customer_1

The URLs on the SolrCloud page have been updated - this would now be
http://localhost:8983/solr/collection1/select?distrib=true&shards=customer_1

This will work as long as no customer becomes bigger than a shard.  If
that's not the case, you could query the entire collection and filter
on customer_1, or create a collection per customer (or do both, if you
mave many small customers that you want to pack in a single shard).

http://localhost:8983/solr/collection1/select?distrib=true&collection=customer_1

> Reading over some of the previous discussions, slices seem to be
> somewhat contentious, and I wanted to chime in on them a bit here. It
> seems to me that slices are loosely defined, and I think thats a good
> thing. If you think of slices as being similar to tags, then its easy
> to imagine that any given shard can belong to many different slices.

I wouldn't call it a "slice" but I've also been thinking about how to
select groups of nodes.
Extending that to shards would also make sense.

-Yonik
http://www.lucidimagination.com

Reply via email to