Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (herse.apache.org: domain of rosherd@googlemail.com
 designates 64.233.184.225 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=ebubb6ji/6ve5jlgs+MtVOatl5WtjmRLMV6+ZBSKU0msUIE/nEFwcnpI381dkpCpUVmknfIy1ErQ4tzoLGhQyPcYm+rqfkMZ1hXTWzNADJE1dTpZxnTogCX0Feq+G2h/b2+ViNX6VgyilWv00rIgu4i0gFJ3a7AIySl/qAt8Xyk=
Message-ID: <1c36b0de0704030733s44aec318id2bfe58c44dbaa13@mail.gmail.com>
Date: Tue, 3 Apr 2007 15:33:08 +0100
From: "Daniel Rosher" <rosherd@googlemail.com>
To: java-user@lucene.apache.org
Subject: Re: Design Problem: Searching large set of protected documents
In-Reply-To: 
 <OF8304FC9E.E340D68F-ON802572B2.004D0CC2-802572B2.004DC797@xcom.de>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_10012_4391101.1175610788834"
References: <1174299031.6246.13.camel@localhost>
	 <OF8304FC9E.E340D68F-ON802572B2.004D0CC2-802572B2.004DC797@xcom.de>

------=_Part_10012_4391101.1175610788834
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi Jonathon,

Since the number of users in your application is small, perhaps you could
apply a pre-generated filter per user, and apply this to the search, howeve=
r
this won't scale well if the number of users grow.

Another idea might be to have several filters,each of which detail a
particular type of access rather than a filter / user. Then using the
ChainedFilter chain together these filters, depending on the user, at query
time.

Regards,
Dan

On 4/3/07, Jonathan O'Connor <jonathan.oconnor@xcom.de> wrote:
>
> Hi,
> I have a database of a million documents and about 100 users. The
> documents
> can have an access control list, and there is a complex, recursive
> algorithm to say if a particular user can see a particular document.
>
> My problem is that my search algorithm is to first do a standard lucene
> search for matching documents, and then check security on each one found,
> just returning the allowed documents. However, if I do this, and the
> lucene
> returns 100000 docs, but the user can only see 10 of these, then obviousl=
y
> the search is going to take an awful long time.
>
> Has anyone come across this problem before, and if so what approach did
> you
> take? I guess I could precalculate the permissions for every user-documen=
t
> pair, but that's alot of storage, and a lot of precalculation!
>
> I await the list's accumulated wisdom with eagerness and interest.
> Thanks,
> Jonathan O'Connor
> XCOM Dublin
>
>
>
> *** XCOM AG Legal Disclaimer ***
>
> Diese E-Mail einschliesslich ihrer Anhaenge ist vertraulich und ist allei=
n
> f=FCr den Gebrauch durch den vorgesehenen Empfaenger bestimmt. Dritten is=
t
> das Lesen, Verteilen oder Weiterleiten dieser E-Mail untersagt. Wir
> bitten,
> eine fehlgeleitete E-Mail unverzueglich vollstaendig zu loeschen und uns
> eine Nachricht zukommen zu lassen.
>
> This email may contain material that is confidential and for the sole use
> of the intended recipient. Any review, distribution by others or
> forwarding
> without express permission is strictly prohibited. If you are not the
> intended recipient, please contact the sender and delete all copies.
>
> Hauptsitz: Bahnstrasse 37, D-47877 Willich, USt-IdNr.: DE 812 885 664
> Kommunikation: Telefon +49 2154 9209-70, Telefax +49 2154 9209-900,
> www.xcom.de
> Handelsregister: Amtsgericht Krefeld, HRB 10340
> Vorstand: Matthias Albrecht, Renate Becker-Grope, Marco Marty, Dr. Rainer
> Fuchs
> Vorsitzender des Aufsichtsrates: Stephan Steuer

------=_Part_10012_4391101.1175610788834--