Re: Design guidance - search strategy

2008-12-05 Thread Otis Gospodnetic
:20 AM > Subject: Re: Design guidance - search strategy > > Glad it's working, but it's not my book, that's Erik Hatcher not > Erick Erickson. > > Erik: > Do I get a commission? > > On Thu, Dec 4, 2008 at 9:48 PM, Ian Vink wrote: > > > It wo

Re: Design guidance - search strategy

2008-12-05 Thread Erick Erickson
Glad it's working, but it's not my book, that's Erik Hatcher not Erick Erickson. Erik: Do I get a commission? On Thu, Dec 4, 2008 at 9:48 PM, Ian Vink <[EMAIL PROTECTED]> wrote: > It works. > For those using Lucene.NET here is an example of a Filter that takes a list > of IDs for books: > >

Re: Design guidance - search strategy

2008-12-04 Thread Ian Vink
It works. For those using Lucene.NET here is an example of a Filter that takes a list of IDs for books: public class BookFilter: Filter { private readonly List bookIDs; public BookFilter(List bookIDsToSearch) { bookIDs = bookIDsToSearch; }

Re: Design guidance - search strategy

2008-12-04 Thread Ian Vink
I bought your book :) Thanks, I will look into it. On Thu, Dec 4, 2008 at 6:12 PM, Erick Erickson <[EMAIL PROTECTED]>wrote: > See the class in the docs or Lucene In Action for more > detail, but here's the short form. > > A Filter is a bitset where each bit's ordinal position stands > for a d

Re: Design guidance - search strategy

2008-12-04 Thread Erick Erickson
See the class in the docs or Lucene In Action for more detail, but here's the short form. A Filter is a bitset where each bit's ordinal position stands for a document. I.e. bit 1 means doc id 1, bit 519 represents document 519 etc. When you pass a filter to one of the search routines that acc

Re: Design guidance - search strategy

2008-12-04 Thread Ian Vink
So, let me get this straight. :) A Query tells Lucene what to search for. Then a Filter tells lucene what? I think I'm missing understanding about what a Filter is for. Ian On Thu, Dec 4, 2008 at 9:36 AM, Erick Erickson <[EMAIL PROTECTED]>wrote: > It's generally a bad idea to iterate a Hits

Re: Design guidance - search strategy

2008-12-04 Thread Erick Erickson
It's generally a bad idea to iterate a Hits object. In fact, Hits is deprecated in recent versions of Lucene. The underlying problem is that the query is re-executed every 100 responses or so. First suggestion, create a Filter by iterating over your docid field and use that in your searches see se

Design guidance - search strategy

2008-12-04 Thread Ian Vink
I have documents with this simple schema in Lucene which I can not change. docid: (int) contents: (text) The user is given a list of 10,000 documents in a tree which they select to search, usually they select 5000 or so. I only want to search those 5000 documents. I have the 'id' fields. That is