I was just reading about the limit on boolean operators in a query (it seems to default to 1024 in Solr).
Using option 2 would mean that a user can't be in any more than 1024 communities (assuming no other boolean logic in the query). Potentially a huge number of communities (10,000+ ?). Each community could easily have say 100 documents each, and there's some other "global" type documents too. Say 500,000 - 1,000,000 documents? What do you mean by "You could also store user documents in the collection to avoid passing the security info" ? I'm not really a Java programmer of any significance, but I work with people who are, and I can bully them into helping out. (I'm a Perl guy myself). Thanks, -- Martyn On Thu, 2006-08-10 at 23:43 -0400, Yonik Seeley wrote: > On 8/10/06, Martyn Smith <[EMAIL PROTECTED]> wrote: > > I'm trying to index data in a system that implements some rather nasty > > access controls on the data. > > > > Basically, there are users, and communities, and users are members of > > the communities. Potentially a user could be a member of hundreds or > > even thousands of communities (there's no enforced upper limit). > > I think option 2 (storing the community id with the document) is the way to > go. > If it's not fast enough, custom query handlers and using filters may help. > You could also store user documents in the collection to avoid passing > the security info (this would definitely require a custom query > handler). > > What are the number of documents, and number of communities? > > -Yonik >
