Hi, all
I found KeywordAnalyzer/KeywordTokenizer on trunk has a problem.
These have a condition(tokenStreams in Analyzer and done in KeywordTokenizer),
but these don't reset the condition. So KeywordAnalyzer can't analyze
a field more then twice.
I already created a patch for this problem.
Can I
[
https://issues.apache.org/jira/browse/LUCENE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552322
]
Doron Cohen commented on LUCENE-997:
Sean, can you revise your patch to follow the suggestions above?
That is, c
For those who don't recall, TeeTokenFilter was added on https://issues.apache.org/jira/browse/LUCENE-1058
to handle what I would consider a somewhat common case whereby two
or more fields share a fair number of common analysis steps. For
instance, if one wanted a field that contained the pro
[
https://issues.apache.org/jira/browse/LUCENE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552295
]
Yonik Seeley commented on LUCENE-997:
-
{quote}make TimeLimitedCollector be a front-end for another collector (for
Thanks you all. Do you think such a feature will ever be included in
Lucene "standard"?
MC
On 12/15/07, Timo Nentwig <[EMAIL PROTECTED]> wrote:
> On Friday 14 December 2007 16:56:07 Sean Timm wrote:
> > See LUCENE-997
> > https://issues.apache.org/jira/browse/LUCENE-997
>
> I actually have had th
: I'm against caching in general because you always run into some hard to
: understand and examine problem but this seems to be one of the rare cases
: where caching makes sense.
For you maybe, but i've actually seen very few instances in practice where
people who are speed concious use FuzzyQ
: > Hoss means calling rewrite on the *result* of a rewrite.
:
: Uh? That's what I mean (propose), too... But currently nothing's cached at
: all.
:
: Cache the result (BooleanQuery) of rewrite() in a WeakHashMap with key =
: IndexReader and value = LRU.
yes .. you can do that. you don't nee
