as permissions and adding this
> restrictions to the solr query. this way you can't change reps'permissions
> without re-indexing. so the query for solr if the current user is allowed
> for search in the 1 and 2 reps should be something like ...rep_id:1OR2...
>
>
> Alex
ust have to take a look on
> the db and include the repository name in the index. so you just have to
> control (using query parameters) if the query is done for the right reps for
> that user.
>
> is it good for u?
>
>
>
> On Wed, Mar 25, 2009 at 6:20 PM, Jesper N
he 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 wrote:
>
>> On Wed, Mar 25, 2009 at 5:57 PM, Eric Pugh
>&g
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.
>>
&
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.
