t;java-user@lucene.apache.org<mailto:java-user@lucene.apache.org>"
mailto:java-user@lucene.apache.org>>
Subject: PerFieldAnalyzerWrapper does not seem to allow use of a custom analyzer
I can’t seem to detect any issues with the final custom analyzer declared in
this code snippet (Th
assume it’s just
falling to the StandardAnalyzer I’ve declared as default in the
PerfieldAnalyzerWrapper. The other inner Anonymous declarations seem to work
fine and I can see them hit a breakpoint. I don’t have any errors to standard
out or to my logs. Is there something obviously wrong with
quot;, new KeywordAnalyzer());
...
...
return new PerFieldAnalyzerWrapper(new CustomAnalyzer(), analyzerMap) ;
}
}
Which is much simpler than all of the things I was thinking I would need to do.
Thanks very much,
Mike
-Original Message-
From: Chris Male [mailto:gento...@gmail.
e
> protected Analyzer getWrappedAnalyzer(String fieldName) {
> Analyzer analyzer;
>
> if (analyzerMap.containsKey(fieldName) {
> analyzer = analyzerMap.get(fieldName);
> } else {
> analyzer = defaultAnalyzer;
> }
> }
>
am);
}
}
-Original Message-
From: Chris Male [mailto:gento...@gmail.com]
Sent: Tuesday, September 25, 2012 5:34 PM
To: java-user@lucene.apache.org
Subject: Re: Lucene 4.0 PerFieldAnalyzerWrapper question
Ah I see.
The problem is that we don't really encourage wrapping of Anal
Ah I see.
The problem is that we don't really encourage wrapping of Analyzers. Your
Analyzer wraps a PerFieldAnalyzerWrapper consequently it needs to extend
AnalyzerWrapper, not Analyzer. AnalyzerWrapper handles the
createComponents call and just requires you to give it the Analyzer(s)
y
Hi Chris,
In a nutshell, my question is, what should I put in place of ??? to make this
into a Lucene 4.0 analyzer?
public class MyPerFieldAnalyzer extends Analyzer {
PerFieldAnalyzerWrapper _analyzer;
public MyPerFieldAnalyzer() {
Map analyzerMap = new HashMap();
analyzerMap.put
Hi Mike,
I don't really understand what problem you're having.
PerFieldAnalyzerWrapper, like all AnalyzerWrappers, uses
Analyzer.PerFieldReuseStrategy which means it caches the
TokenStreamComponents per field. The TokenStreamComponents cached are
created by by retrieving the wrappe
I am updating an analyzer that uses a particular configuration of the
PerFieldAnalyzerWrapper to work with Lucene 4.0. A few of the fields use a
custom analyzer and StandardTokenizer and the other fields use the
KeywordAnalyzer and KeywordTokenizer. The older version of the analyzer looks
like
Hello~
Have anyone needed a method, getAnalyzer(String fieldName) of
PerFieldAnalyzerWrapper class, so far?
A method getDefaultAnalyzer() as well.
It is useful in my project.
The needs would be unusual, though. Implementing these methods is very simple.
Does Apache Lucene have any plan to
On 04/05/2011 07:56, Israel Tsadok wrote:
On Tue, May 3, 2011 at 7:03 PM, Paul Taylor <mailto:paul_t...@fastmail.fm>> wrote:
We subclassed PerFieldAnalyzerWrapper as follows:
public class PerFieldEntityAnalyzer extends PerFieldAnalyzerWrapper {
public PerFieldEntit
On Tue, May 3, 2011 at 7:03 PM, Paul Taylor wrote:
> We subclassed PerFieldAnalyzerWrapper as follows:
>
> public class PerFieldEntityAnalyzer extends PerFieldAnalyzerWrapper {
>
>public PerFieldEntityAnalyzer(Class indexFieldClass) {
>super(new Standa
We subclassed PerFieldAnalyzerWrapper as follows:
public class PerFieldEntityAnalyzer extends PerFieldAnalyzerWrapper {
public PerFieldEntityAnalyzer(Class indexFieldClass) {
super(new StandardUnaccentAnalyzer());
for(Object o : EnumSet.allOf(indexFieldClass
I can see no error,
Are you sure, that you are really using the PerFieldAnalyzerWrapper for both
indexing and searching? Field names are case sensitive! How does your index
look like with Luke?
Can you send us the code to reproduce this? E.g. some small 2.4.1 index
attached as zip and code that
One small correction...
My default Analyzer is snowball analyzer and it is being used for all fields
(not KeywordAnalyzer) even though few fields should use different analyzer.
PerFieldAnalyzerWrapper is not considering the analyzer set for different
fields.
This is consistently reproducing
Hello all,
I am having an index build using v2.4.1. I upgraded to 2,9.1. The index was
searchable. I added couple of documents and i found that the
PerFieldAnalyzerWrapper is not working as expected.
PerFieldAnalyzerWrapper analyzer = new PerFieldAnalyzerWrapper(getAnalyser
uot;hello world"
> string[] fields = new string[] { "name", "keyword", "shortDescription" };
>
> string strSearchTerm = "hello world";
> PerFieldAnalyzerWrapper wrapper = new PerFieldAnalyzerWrapper(new
> StandardAnalyzer());
> wrapper.AddAnalyzer(&qu
fields = new string[] { "name", "keyword", "shortDescription" };
string strSearchTerm = "hello world";
PerFieldAnalyzerWrapper wrapper = new PerFieldAnalyzerWrapper(new
StandardAnalyzer());
wrapper.AddAnalyzer("keyword", new KeywordAnalyzer())
ct: Re: PerFieldAnalyzerWrapper use? Analyzer's not being used as
expected
This look better?
// Check to see if index exists.
// If it doesn't, then set createIndex boolean to true
boolean createIndex = false;
if (!IndexReader.inde
Or simpler:
wr = new IndexWriter(indexDir, aWrapper, !IndexReader.indexExists(indexDir));
- Original Message
From: Michael J. Prichard <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Sunday, July 30, 2006 1:35:29 PM
Subject: Re: PerFieldAnalyzerWrapper use? Analyzer
3 PM
Subject: Re: PerFieldAnalyzerWrapper use? Analyzer's not being used as
expected
Hey Erik,
Will do. May I ask why? Out of curiousity.
Thanks,
Michael
Erik Hatcher wrote:
I think you should use a new instance of each analyzer for each
field, not reuse instances. Other than tha
.apache.org
Sent: Saturday, July 29, 2006 4:04:23 PM
Subject: Re: PerFieldAnalyzerWrapper use? Analyzer's not being
used as expected
Hey Erik,
Will do. May I ask why? Out of curiousity.
Thanks,
Michael
Erik Hatcher wrote:
I think you should use a new instance of each analyze
IndexWriter ctor.
Otis
- Original Message
From: Michael J. Prichard <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Saturday, July 29, 2006 4:04:23 PM
Subject: Re: PerFieldAnalyzerWrapper use? Analyzer's not being used as
expected
Hey Erik,
Will do. May I ask w
:
So I have the following code...
// let's get our SynonymAnalyzer
SynonymAnalyzer synAnalyzer = getSynonymAnalyzer();
// let's get our EmailAnalyzer
EmailAnalyzer emailAnalyzer = getEmailAnalyzer();
// set up perfieldanalyzer
PerFieldAnalyzerWrapper aWrapper = new PerFieldAnalyzerW
lyzer synAnalyzer = getSynonymAnalyzer();
// let's get our EmailAnalyzer
EmailAnalyzer emailAnalyzer = getEmailAnalyzer();
// set up perfieldanalyzer
PerFieldAnalyzerWrapper aWrapper = new PerFieldAnalyzerWrapper(new
StandardAnalyzer()); aWrapper.addAnalyzer("subject&
wrote:
So I have the following code...
// let's get our SynonymAnalyzer
SynonymAnalyzer synAnalyzer = getSynonymAnalyzer();
// let's get our EmailAnalyzer
EmailAnalyzer emailAnalyzer = getEmailAnalyzer();
// set up perfieldanalyzer
PerFieldAnalyzerWrapper aWrapper = new PerFieldAnaly
So I have the following code...
// let's get our SynonymAnalyzer
SynonymAnalyzer synAnalyzer = getSynonymAnalyzer();
// let's get our EmailAnalyzer
EmailAnalyzer emailAnalyzer = getEmailAnalyzer();
// set up perfieldanalyzer
PerFieldAnalyzerWrapper aWrapper = new PerFieldAnalyzerW
27 matches
Mail list logo
