Then we agree, and it is StopFilter that needs to be patched to take
into account the number of removed terms, and add appropriate
positional info to each term.
Otis
--- Erik Hatcher <[EMAIL PROTECTED]> wrote:
> On Tuesday, October 21, 2003, at 07:31 PM, Otis Gospodnetic wrote:
> > So "phone boy" would match documents containing "phone the boy"?
> That
> > doesn't sound right to me, as it assumes what the user is trying to
> do.
>
> That is correct.... currently a match would be found. Here's a
> little
> test case I'm working with:
>
> Directory directory = new RAMDirectory();
> IndexWriter writer = new IndexWriter(directory, new
> StandardAnalyzer(), true);
> Document doc = new Document();
> doc.add(Field.Text("contents", "The quick brown fox jumped over
> the
> lazy dogs"));
> writer.addDocument(doc);
> writer.close();
>
> IndexSearcher searcher = new IndexSearcher(directory);
> QueryParser parser = new QueryParser("contents", new
> StandardAnalyzer());
> Query query = parser.parse("\"over lazy\"");
>
> Hits hits = searcher.search(query);
> assertEquals(1, hits.length());
>
> which currently passes.... although should not I don't think.
>
> > Wouldn't it be better to allow the user to decide what he wants?
> > (i.e. "phone boy" returns documents with that _exact_ phrase.
> "phone
> > boy"~2 also returns documents containing "phone the boy").
>
> I concur. StopFilter just removes terms, but does not adjust the
> following acceptable term with the offset to account for the missing
> stop words.
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
