lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doron Cohen (JIRA)" <>
Subject [jira] Commented: (LUCENE-966) A faster JFlex-based replacement for StandardAnalyzer
Date Wed, 01 Aug 2007 22:24:52 GMT


Doron Cohen commented on LUCENE-966:

The search quality test failure can be caused by the standard 
analyzer generating different tokens than before. (has nothing 
to do with token types.)

This is because the test's topics (queries) and qrels (expected matches) 
were created by examining an index that was created using the current 
standard analyzer. Now, running this test with an analyzer that creates 
other tokens is likely to fail. 

It is not difficult to update this test for a modified analyzer, but it seems 
better to me to preserve the original standard analyzer behavior.

> A faster JFlex-based replacement for StandardAnalyzer
> -----------------------------------------------------
>                 Key: LUCENE-966
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Analysis
>            Reporter: Stanislaw Osinski
>             Fix For: 2.3
>         Attachments:, jflex-analyzer-patch.txt, jflex-analyzer-r560135-patch.txt,
jflex-analyzer-r561292-patch.txt, jflex-analyzer-r561693-compatibility.txt
> JFlex ( can be used to generate a faster (up to several times) replacement
for StandardAnalyzer. Will add a patch and a simple benchmark code in a while.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message