lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Male (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (LUCENE-3389) Add ReuseStrategy to ReusableAnalyzerBase
Date Mon, 22 Aug 2011 07:12:29 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Male resolved LUCENE-3389.
--------------------------------

    Resolution: Won't Fix

As it turns out this is best to do as part of a larger collapsing of ReusableAnalyzerBase
into Analyzer (as the access to the tokenstreams ThreadLocal is a little messy).

I'll tackle it when I do the collapsing.

> Add ReuseStrategy to ReusableAnalyzerBase
> -----------------------------------------
>
>                 Key: LUCENE-3389
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3389
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: modules/analysis
>            Reporter: Chris Male
>
> ReusableAnalyzerBase currently ignores the fieldName passed into .tokenStream/.reusableTokenStream
and reuses the same components for every field.  To move all Analyzers over to using ReusableAnalyzerBase,
we need to support per-field reuse as well.
> As Robert pointed out in LUCENE-2309, we can do this by adding a ReuseStrategy which
has two impls; one implementing the current global behavior and one providing per-field reuse.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


Mime
View raw message