Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <AANLkTil7NfUPftjBapfn9qoWbJNtun3FhGG-IXBKq9lk@mail.gmail.com>
References: <AANLkTil7NfUPftjBapfn9qoWbJNtun3FhGG-IXBKq9lk@mail.gmail.com>
Date: Thu, 22 Jul 2010 05:20:15 -0400
Message-ID: <AANLkTinGLNQVUfu2qZa2A_ySXpbRZGEgM44QzccmAqQm@mail.gmail.com>
Subject: Re: on-the-fly "filters" from docID lists
From: Michael McCandless <lucene@mikemccandless.com>
To: java-user@lucene.apache.org
Content-Type: text/plain; charset=ISO-8859-1

It sounds like you should implement a custom Filter?

Its getDocIdSet would consult your foreign key-value store and iterate
through the allowed docIDs, per segment.

Mike

On Wed, Jul 21, 2010 at 8:37 AM, Martin J <martinj.engine@gmail.com> wrote:
> Hello, we are trying to implement a query type for Lucene (with eventual
> target being Solr) where the query string passed in needs to be "filtered"
> through a large list of document IDs per user. We can't store the user ID
> information in the lucene index per document so we were planning to pull the
> list of documents owned by user X from a key-value store at query time and
> then build some sort of filter in memory before doing the Lucene/Solr query.
> For example:
>
> content:"cars" user_id:X567
>
> would first pull the list of docIDs that user_id:X567 has "access" to from a
> keyvalue store and then we'd query the main index with content:"cars" but
> only allow the docIDs that came back to be part of the response. The list of
> docIDs can near the hundreds of thousands.
>
> What should I be looking at to implement such a feature?
>
> Thank you
> Martin
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org