The SolrCloud capabilities are pretty new to me too, but I doubt
anything like this is built in, you're probably better off with your
current solution.

Although one wonders if some kind of group-based permission
scheme would work for you. Essentially you add an
authorized_users entry to each document at index time and
then simply form an fq=auth_token:(123 2348 238....). This only
works if the total number of tokens a user can have is relatively
small....

Best
Erick

On Thu, Jan 12, 2012 at 5:13 AM, Jaran Nilsen <jaran.nil...@gmail.com> wrote:
> Hi.
>
> We're currently looking at SolrCloud to improve management of our Solr
> cluster. There is one use case which I am wondering if SolrCloud provide
> any support for out of the box, or if our best bet is to stick with our
> current solution.
>
> The use case is:
>
> We have a large number of shards, using the same schema - so, perfect for
> SolrCloud. Some of these shards should have restricted access, meaning only
> customers with certain privileges will be able to query them. The way we
> solve this today is to maintain a database listing those users who have
> access to these restricted shards. When building the shards-parameter for
> querying Solr, we then use this database to append the URLs of the
> restricted shards ONLY if the user has access to them.
>
> With SolrCloud it would be great to be able to use the distrib=true
> parameter, but that would override the approach we're currently using.
>
> My questions are:
>
> 1. would it be an idea to create a separate collection for the shards that
> are restricted? If so, is there currently any support for specifying which
> collections to search so that we could implement the solution outlined
> above, but for collections rather than shards?
>
> 2. If no-go on #1, are we better off sticking with our current approach and
> skip using distrib=true which would query all shards?
>
> Any input appreciated!
>
> Best,
> Jaran
>
> --
> Jaran Nilsen
> Skype: jaran.nilsen
> jarannilsen.com || codemunchies.com || notpod.com
> twitter.com/jarannilsen // www.linkedin.com/in/jarannilsen //
> facebook.com/jaran.nilsen

Reply via email to