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 > > > > >
