Hm, I must be missing something, then. Consider this.
There are three repositories, A and B, C. There are two users, U1 and U2. Repository A is public, while B and C are private. Only U1 can access B. No one can access C. I index this data, such that Is_Private is true for B. Now, when U2 searches, he will only see data for repo A. This is correct. When U1 searches, what happens? AFAIK, he will also only see data for A, unless we specify Is_Private:True, but then he will only see data for B (and C, which he doesn't have access to.) Secondly, say we grant U2 access to B. How do we tell Solr that he can see it, then? Sorry if I'm not making much sense here, but I'm quite confused. Jesper On Wed, Mar 25, 2009 at 6:13 PM, Alejandro Gonzalez <alejandrogonzalezd...@gmail.com> wrote: > i can't see the problem about that. you can manage your users using a DB and > keep there the permissions they could have, and create or erase users > without problems. you just have to manage a "working index" field for each > user with repositories' ids he can access. or u can create several indexes > and a users solr index with a multi-valued field with the indexes the user > can access. > > if then u want to turn a private repository into public u just have to > change the permissions field in your DB or users' index. > > On Wed, Mar 25, 2009 at 6:02 PM, Jesper Nøhr <jes...@noehr.org> wrote: > >> On Wed, Mar 25, 2009 at 5:57 PM, Eric Pugh >> <ep...@opensourceconnections.com> wrote: >> > You could index the user name or ID, and then in your application add as >> > filter the username as you pass the query back to Solr. Maybe have a >> > access_type that is Public or Private, and then for public searches only >> > include the ones that meet the access_type of Public. >> >> That makes sense. Two questions on that: >> >> 1. More than one user can have access to a repository, so how would >> that work? Also, if a user is added/removed, what's the best way to >> keep that in sync? >> >> 2. In the event that a repository that is private, is made public, how >> easy would it be to run an "UPDATE" so to speak? >> >> >> Jesper >> >> > On Mar 25, 2009, at 12:52 PM, Jesper Nøhr wrote: >> > >> >> Hi list, >> >> >> >> I've finally settled on Solr, seeing as it has almost everything I >> >> could want out of the box. >> >> >> >> My setup is a complicated one. It will serve as the search backend on >> >> Bitbucket.org, a mercurial hosting site. We have literally thousands >> >> of code repositories, as well as users and other data. All this needs >> >> to be indexed. >> >> >> >> The complication comes in when we have private repositories. Only >> >> select users have access to these, but we still need to index them. >> >> >> >> How would I go about accomplishing this? I can't think of a clean way to >> >> do it. >> >> >> >> Any pointers much appreciated. >> >> >> >> >> >> Jesper >> > >> > ----------------------------------------------------- >> > Eric Pugh | Principal | OpenSource Connections, LLC | 434.466.1467 | >> > http://www.opensourceconnections.com >> > Free/Busy: http://tinyurl.com/eric-cal >> > >> > >> > >> > >> > >> >
