Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Users List" <lucene-user@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
From: Paul Elschot <paul.elschot@xs4all.nl>
To: lucene-user@jakarta.apache.org
Subject: Re: restricting search result
Date: Sat, 4 Dec 2004 10:53:34 +0100
User-Agent: KMail/1.5.4
References: <e4ae55b904120314314cfae79b@mail.gmail.com>
In-Reply-To: <e4ae55b904120314314cfae79b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200412041053.34545.paul.elschot@xs4all.nl>

Paul, 

On Friday 03 December 2004 23:31, you wrote:
> Hi,
> how yould you restrict the search results for a certain user? I'm

One way to restrict results is by using a Filter.

> indexing all the existing data in my application but there are certain
> access levels so some users should see more results then an other.
> Each lucene document has a field with an internal id and I want to
> restrict on that basis. I tried it with adding a long concatenation of
> my ids ("+locationId:1 +locationId:3 + ...") but this throws a "More
> than 32 required/prohibited clauses in query." exception.
> Any suggestions?

Using a + before each term requires them all, ie. uses AND, which
would normally have an empty result for an Id field.
You might prefer this query concatenation:

+(locationId:1 locationId:3 ...)

It effectively OR's the locationId content query and requires
only one of the terms to match.

In this case using a Filter would probably be better, though.

Regards,
Paul


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