! Thank you for
the tip! I am reading it's SimplePreAnalyzedParser as we speak!
Best regards,
Guan
-Original Message-
From: Mikhail Khludnev
Sent: Wednesday, April 26, 2023 4:14 PM
To: java-user@lucene.apache.org
Subject: Re: Can an analyzer access other field's data during in
lue() method.
>
> In a nutshell, I will need two parts to make this work:
>
> 1. a custom tokenizer/filter;
> 2. a custom field;
>
> Let me know if there is any caveat...
>
> And thank you so much for guiding me through!
>
> Guan
>
> -Original Messag
stom field;
Let me know if there is any caveat...
And thank you so much for guiding me through!
Guan
-Original Message-
From: Mikhail Khludnev
Sent: Tuesday, April 25, 2023 4:40 AM
To: java-user@lucene.apache.org
Subject: Re: Can an analyzer access other field's data during index
: Monday, April 24, 2023 4:56 PM
> To: java-user@lucene.apache.org
> Subject: Re: Can an analyzer access other field's data during index time?
>
> External Email - Use Caution
>
> Well.. maybe something like
>
> https://lucene.apache.org/core/8_5_1/analyzers-common/org
-user@lucene.apache.org
Subject: Re: Can an analyzer access other field's data during index time?
External Email - Use Caution
Well.. maybe something like
https://lucene.apache.org/core/8_5_1/analyzers-common/org/apache/lucene/analysis/miscellaneous/ConditionalTokenFilter.html
?
On Mon, Apr 24,
> Sent: Monday, April 24, 2023 4:20 PM
> To: java-user@lucene.apache.org
> Subject: Re: Can an analyzer access other field's data during index time?
>
> External Email - Use Caution
>
> Hello Guan.
> It reminds me https://youtu.be/EkkzSLstSAE?t=1531 timecode.
> I'm af
Khludnev
Sent: Monday, April 24, 2023 4:20 PM
To: java-user@lucene.apache.org
Subject: Re: Can an analyzer access other field's data during index time?
External Email - Use Caution
Hello Guan.
It reminds me https://youtu.be/EkkzSLstSAE?t=1531 timecode.
I'm afraid it's quite far from t
Hello Guan.
It reminds me https://youtu.be/EkkzSLstSAE?t=1531 timecode.
I'm afraid it's quite far from the existing codebase where the Field has no
reference to enclosing Document. sigh.
On Mon, Apr 24, 2023 at 6:00 PM Wang, Guan wrote:
> Hi,
>
> I understand Lucene analyzer
Hi,
I understand Lucene analyzer is per field basis. But I wonder if it's even
possible for an analyzer on field A to be able to access data in field B during
the index process on any stage, saying CharFilter, Tokenizer or TokenFilter?
I'd like to control the behavior of the indexi
alyzer classes, which implement a couple of methods that add
TokenFilters to process the tokens. The base class for the rest of
implementations is the following one.
public class StandardCustomAnalyzer implements CustomAnalyzer {
private final Analyzer analyzer;
public StandardCusto
I think you'll need a SpanQuery with the inOrder flag set:
https://lucene.apache.org/core/8_8_1/core/org/apache/lucene/search/spans/SpanNearQuery.html
Charlie
On 17/03/2021 10:30, Vlad Smirnovskiy wrote:
Hello!
I`d like to do something like that: When I add a document and some text is
going wi
Hello!
I`d like to do something like that: When I add a document and some text is
going with (e.g.) quotes it should mean that this text has to be exactly in
the query. Better with an examples -
text: green "blue apple" juice
query : blue apple - result: hit.
query : blue apple juice - result: h
You can check how SolrAnalyzer switches chains across fields.
On Tue, Dec 10, 2019 at 9:41 AM 小鱼儿 wrote:
> Directory indexDataDir = FSDirectory.open(Paths.get("index_data"));
> Analyzer analyzer = MyLuceneAnalyzerFactory.newInstance();
> IndexWriterConfig iwc = new IndexWr
Directory indexDataDir = FSDirectory.open(Paths.get("index_data"));
Analyzer analyzer = MyLuceneAnalyzerFactory.newInstance();
IndexWriterConfig iwc = new IndexWriterConfig(analyzer);
iwc.setOpenMode(OpenMode.CREATE);
iwc.setRAMBufferSizeMB(256.0);
IndexWriter indexWriter = new I
>
> >> I can use StandardAnalyzer or WhitespaceAnalyzer but I want to
> >tokenize on
> >> underscores also
> >> which these analyzers don't do. I have also looked at
> >WordDelimiterFilter
> >> which will split "axt1234" into "a
zer but I want to
>tokenize on
>> underscores also
>> which these analyzers don't do. I have also looked at
>WordDelimiterFilter
>> which will split "axt1234" into "axt" and "1234". However, using this
>also,
>> I cannot search for &q
;1234". However, using this also,
> I cannot search for "axt12" etc.
>
> Is there something like an Alphanumeric analyzer which would be very
> similar to SimpleAnalzyer but in addition to letters it would also keep
> digits in its tokens? I am willing contribute such an analyzer if one is
> not available.
>
> Thanks and Regards,
> Abhishek
>
>
>
Hi,
The easiest is to use PatternTokenizer as part of your analyzer. It uses a
regular expression to split words. Just use some regular expression that
matches unicode ranges for numbers and digits.
To build your Analyzer use the class CustomAnalyzer and its builder API to
construct your own
xt1234" into "axt" and "1234". However, using this also,
I cannot search for "axt12" etc.
Is there something like an Alphanumeric analyzer which would be very
similar to SimpleAnalzyer but in addition to letters it would also keep
digits in its tokens? I am willing contribute such an analyzer if one is
not available.
Thanks and Regards,
Abhishek
pply "CommonGramsFilterFactory" and "StopFilterFactory" in the
query analyzer for our solr environment, while this issue cause some query get
empty result.
The issue can be reproduce by the steps in LUCENE-7698 and just change the
query string to "hello with an accent&quo
there really should be an extension of
the Analyzer api to include a generic argument of abstract class
AnalyzerContext that could optionaly be used via IndexWriter snd IndexSearcher
to supply useful context information from the caller to IndexWriter and
IndexSearcher.
This would require threading
s for different inputs. Doing this requires extra
context when choosing the analyzer (our the token streams that it
generates) as you say. See http://issues.apache.org/jira/browse/LUCENE-8240
for one idea of how to accomplish this.
On Wed, Apr 11, 2018, 9:34 AM Chris Tomlinson
wrote:
> Hello,
.
For Chinese, for example, we have an analyzer that creates a TokenStream of
Pinyin with diacritics for any of the input encodings. Thus it is possible in
some situations to retrieve documents originally input as zh-hans and so on.
The same applies to the other languages.
One objective is to
Hi Team,
I have a doubt on parsing a query using
MultiFieldQueryParser over StandardAnalyzer.
searchWord: abc.def_...@global-international.com
while performing a search using the code,
Analyzer analyzer = new StandardAnalyzer(Version.LUCENE_40, new
> StringRea
acets).
>
> Uwe
>
> -
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
> > -Original Message-
> > From: Armins Stepanjans [mailto:armins.bagr...@gmail.com]
> > Sent: Tuesday, January 9, 2018 2:52 PM
nal Message-
> From: Armins Stepanjans [mailto:armins.bagr...@gmail.com]
> Sent: Tuesday, January 9, 2018 2:52 PM
> To: java-user@lucene.apache.org
> Subject: Analyzer is not called upon executing addDocument()
>
> Hi,
>
> When I create a document with multiple
Hi,
When I create a document with multiple StringFields and add it to
IndexWriter using addDocument(Document), the StringFields within the
Document are not tokenized nor filtered according to Analyzer's
specifications, however when I test my Analyzer, while looping through
tokens by expli
Head meet brick. Thank you, Uwe!
-Original Message-
From: Uwe Schindler [mailto:u...@thetaphi.de]
Sent: Friday, June 23, 2017 11:23 AM
To: java-user@lucene.apache.org
Subject: RE: Extending Analyzer at runtime
Hi,
Or just use CustomAnalyzer, shipped with Lucene since version 5.0. No
re.org]
> Sent: Friday, June 23, 2017 3:55 PM
> To: java-user@lucene.apache.org; nb...@ebi.ac.uk
> Subject: RE: Extending Analyzer at runtime
>
> I plagiarized Solr's org.apache.solr.analysis.TokenizerChain to read the
> configuration from a json file:
>
> https://github.com/
Thanks Alan,
I will take a look at it.
Nicola
-- Original message--From: Alan WoodwardDate: Fri, 23 Jun 2017 14:55To:
java-user@lucene.apache.org;nb...@ebi.ac.uk;Cc: Subject:Re: Extending Analyzer
at runtime
Hi,
You should be able to use AnalyzerWrapper for this, adding your TokenFilters
Hi,
You should be able to use AnalyzerWrapper for this, adding your TokenFilters in
wrapComponents().
Alan Woodward
www.flax.co.uk
> On 23 Jun 2017, at 14:33, Nicola Buso wrote:
>
> Hi,
>
> maybe it's a known question but I could not find and answer.
> I need to base
gramreaper just yet, but that might give
you some ideas.
-Original Message-
From: Nicola Buso [mailto:nb...@ebi.ac.uk]
Sent: Friday, June 23, 2017 9:34 AM
To: java-user
Subject: Extending Analyzer at runtime
Hi,
maybe it's a known question but I could not find and answer.
I
Hi,
maybe it's a known question but I could not find and answer.
I need to base an Analyzer on another Analyzer at runtime.
I know that the Analyzer is a factory and I should really look at
combine the Filters. I'm looking for a way to get the
TokenStreamComponents from an analyzer
imiterGraphFilter.java that passed
> for me:
>
> -
> public void testEmail() throws Exception {
> final int flags = GENERATE_WORD_PARTS | GENERATE_NUMBER_PARTS |
> SPLIT_ON_CASE_CHANGE | SPLIT_ON_NUMERICS | PRESERVE_ORIGINAL;
> Analyzer a = new Analyzer() {
> @Ove
for me:
-
public void testEmail() throws Exception {
final int flags = GENERATE_WORD_PARTS | GENERATE_NUMBER_PARTS |
SPLIT_ON_CASE_CHANGE | SPLIT_ON_NUMERICS | PRESERVE_ORIGINAL;
Analyzer a = new Analyzer() {
@Override public TokenStreamComponents createComponents(String
Hi All,
i want to index email fields as both analyzed and not analyzed using custom
analyzer.
for example,
sm...@yahoo.com
will.sm...@yahoo.com
that is, indexing sm...@yahoo.com as single token as well as analyzed
tokens in same email field...
My existing custom analyzer,
public class
I didn't quite get your idea.
I want to get an analyzer like standard analyzer but with punctuation
customized.
I think one way is customizing an analyzer with a customizer tokenizer
like StandardTokenizer.
In my tokenizer I will re-write StandardTokenizerImpl which seems a little
complica
： java-user@lucene.apache.org
主题： Re: any analyzer will keep punctuation？
Hi Ahmet,
Thanks for your reply, but I didn't quite get your idea.
I want to get an analyzer like standard analyzer but with punctuation
customized.
I think one way is customizing an analyzer with a customizer tokenizer
Hi Ahmet,
Thanks for your reply, but I didn't quite get your idea.
I want to get an analyzer like standard analyzer but with punctuation
customized.
I think one way is customizing an analyzer with a customizer tokenizer
like StandardTokenizer.
In my tokenizer I will re-
(" +
searchphrase + ")";
in this case the value of the field singername will not be analyzed by
the standard analyzer.
On 06.03.2017 09:15, Yonghui Zhao wrote:
Lucene standard anlyzer will remove almost all punctuation.
In some cases, we want to keep some punctuation, for
Hi Zhao,
WhiteSpace tokeniser followed by a customised word delimiter filter factory
would be solution.
Please see types attribute of the word delimiter filter for customising
characters.
ahmet
On Monday, March 6, 2017 12:22 PM, Yonghui Zhao wrote:
Yes whitespace analyzer will keep
keep into something that
StandardTokenizer would not split on.
Mike McCandless
http://blog.mikemccandless.com
On Mon, Mar 6, 2017 at 5:22 AM, Yonghui Zhao wrote:
> Yes whitespace analyzer will keep punctuation, but it only breaks word by
> space.
>
>
> I didn’t explain my requ
Yes whitespace analyzer will keep punctuation, but it only breaks word by
space.
I didn’t explain my requirement clearly.
I want to an analyzer like standard analyzer but may keep some punctuation
configured.
2017-03-06 18:03 GMT+08:00 Ahmet Arslan :
> Hi,
>
> Whitespace analyser/
punctuation.
Is there any analyzer that we can customized punctuation to be removed?
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
Lucene standard anlyzer will remove almost all punctuation.
In some cases, we want to keep some punctuation, for example in music
search, some singer name and album name could be a punctuation.
Is there any analyzer that we can customized punctuation to be removed?
Thank you, works like a charm.
handle the
difference between first call and followup calls. No its quite easy separated:
Create it in one step without a reader and then reuse it as often as you like
by setting a Reader. This is done inside the final Analyzer logic that is
hidden to you!
Uwe
-
Uwe Schindler
Achterdiek 19
Hi all,
I'm porting few classes from 4.8.1 to the newer version of Lucene. I can't
understand how to convert this code, I hope you can help me:
public Analyzer creaAnalyzer() {
return new Analyzer() {
@Override
protected TokenStreamComponents createComponents(String fieldNa
wrote:
> Hello,
>
> I am indexing userAgent fields found in apache logs. Indexing and querying
> everything with
> KeywordAnalyzer - But I found something strange:
>
>
> IndexSearcher searcher = new IndexSearcher(reader);
> Analyzer q_ana
Hello,
I am indexing userAgent fields found in apache logs. Indexing and querying
everything with
KeywordAnalyzer - But I found something strange:
IndexSearcher searcher = new IndexSearcher(reader);
Analyzer q_analyzer = new KeywordAnalyzer();
QueryParser
Hi,
I'm trying to migrate some Analyzers from API 3.6 to 6.2 and I'm not sure
if I got the right approach. I'm using Pylucene, so lets assume this is
pseudo-code.
In 3.x (and up to 4), I've had access to the StringReader containing the
data in the overriden tokenStream(fieldName, reader):
2. [ "ABC", "AB",
"XYZ", "Z"]
Requests that will not match the doc: 1. [ "ABC", "AB", "XYZ"]
2. [ "ABC",
"AB", "XYZ"
ava.nio.file.Path path = FileSystems.getDefault().getPath("D:\\",
"indexRawData");
FSDirectory phraseIndexdir = FSDirectory.open(path);
String fieldContent="Content";
Analyzer analyzerNormal = new StandardAnalyzer();
java.nio.file.Path path2 = FileSystems.getDefault().getP
Hi,
you cannot change the behavior of predefined analyzers! But since Lucene 5
there is no need to write your own subclass to define a custom analyzer. Just
use CustomAnalyzer and define via fluent builder API how your analysis should
look like (see example in javadocs):
https
Dear Users,
I need to develop my language specific analyzer that:
1) does not remove punctuations
2) lowercases and stems each term in the text.
I have tried some of the pre-implemented language analyzer (e.g. German and
Italian analyzers), but they remove punctuation. I/m not sure, but
probably
components in schema are not loaded from runtimelib yet. Only
solrconfig components are loaded from runtime lib a.k.a blob store
On Thu, Sep 10, 2015 at 11:00 PM, Steve Davids wrote:
> Hi,
>
> I am attempting to migrate our deployment process over to using the
> recently added "Blob Store API" wh
> Sent: Thursday, September 10, 2015 7:31 PM
> To: java-user@lucene.apache.org
> Subject: Loading Solr Analyzer from RuntimeLib Blob
>
> Hi,
>
> I am attempting to migrate our deployment process over to using the
> recently added "Blob Store API" which should simpli
Hi,
I am attempting to migrate our deployment process over to using the
recently added "Blob Store API" which should simplify things a bit when it
comes to cloud infrastructures for us. Unfortunately, after loading the jar
in the .system collection and adding it to our runtimelib config overlay
an
I found the problem here. I had changed some method params and was
inadvertently creating the fields I was having issues with as StringFields,
which the analyzer fails silently against.
From: , Scott Bauer mailto:bauer.sc...@mayo.edu>>
Date: Friday, August 7, 2015 at 1:56 PM
To: &quo
I can’t seem to detect any issues with the final custom analyzer declared in
this code snippet (The one that attempts to use a PatternMatchingTokenizer and
is initialized as sa), but it doesn’t seem to be hit when I run my indexing
code despite being in the map. It is indexed finally but I
> userCriteriaProcessed = escape(userCriteria);
> >
> > if (!userCriteria.endsWith(MULTIPLE_CHARACTER_WILDCARD)) {
> > userCriteriaProcessed += MULTIPLE_CHARACTER_WILDCARD;
> > }
> > }
> >
> >
> > String queryStr = "";
&g
ields) {
> String escapedFieldName = escape(fieldName);
> queryStr += String.format("%s:%s ", escapedFieldName,
> userCriteriaProcessed);
> }
>
> query = new QueryParser("", analyzer).parse(queryStr.trim());
>
> ...
>
> On Wed, Jul 22, 201
th(MULTIPLE_CHARACTER_WILDCARD)) {
userCriteriaProcessed += MULTIPLE_CHARACTER_WILDCARD;
}
}
String queryStr = "";
for (String fieldName : fields) {
String escapedFieldName = escape(fieldName);
queryStr += String.format("%s:%s ", escapedFieldName,
userCriteriaProcessed);
{
userCriteriaProcessed += MULTIPLE_CHARACTER_WILDCARD;
}
}
String queryStr = "";
for (String fieldName : fields) {
String escapedFieldName = escape(fieldName);
queryStr += String.format("%s:%s ", escapedFieldName,
curTokenProcessed);
}
query = new QueryPars
Diego Socaceti :
> >
> > > Hi Alessandro,
> > >
> > > yes, i want the user to be able to surround the query with "" to run
> the
> > > phrase query with a NOT tokenized phrase.
> > >
> > > What do i have to do?
> > >
> &g
ave to do?
> >
> > Thanks and Kind regards
> >
> > On Tue, Jul 21, 2015 at 2:47 PM, Alessandro Benedetti <
> > benedetti.ale...@gmail.com> wrote:
> >
> > > Hey Jack, reading the doc :
> > >
> > > " Set to true if phrase queries will be
phrase.
>
> What do i have to do?
>
> Thanks and Kind regards
>
> On Tue, Jul 21, 2015 at 2:47 PM, Alessandro Benedetti <
> benedetti.ale...@gmail.com> wrote:
>
> > Hey Jack, reading the doc :
> >
> > " Set to true if phrase queries will be au
y Jack, reading the doc :
>
> " Set to true if phrase queries will be automatically generated when the
> analyzer returns more than one term from whitespace delimited text. NOTE:
> this behavior may not be suitable for all languages.
>
> Set to false if phrase queries should onl
Hey Jack, reading the doc :
" Set to true if phrase queries will be automatically generated when the
analyzer returns more than one term from whitespace delimited text. NOTE:
this behavior may not be suitable for all languages.
Set to false if phrase queries should only be generated
assic/QueryParserBase.html#setAutoGeneratePhraseQueries(boolean)
-- Jack Krupansky
On Fri, Jul 17, 2015 at 4:41 AM, Diego Socaceti wrote:
> Hi all,
>
> i'm new to lucene and tried to write my own analyzer to support
> hyphenated words like wi-fi, jean-pierre, etc.
> For our customer it
case I identified your requirement, we can have a think to a
solution!
Cheers
2015-07-17 9:41 GMT+01:00 Diego Socaceti :
> Hi all,
>
> i'm new to lucene and tried to write my own analyzer to support
> hyphenated words like wi-fi, jean-pierre, etc.
> For our customer it is imp
Hi all,
i'm new to lucene and tried to write my own analyzer to support
hyphenated words like wi-fi, jean-pierre, etc.
For our customer it is important to find the word
- wi-fi by wi, fi, wifi, wi-fi
- jean-pierre by jean, pierre, jean-pierre, jean-*
The analyzer:
public
gt;> > On Sunday, April 19, 2015 1:37 PM, Lisa Ziri wrote:
>> > Hi,
>> > I'm upgrading to lucene 5.1.0 from lucene 4.
>> > In our index we have documents in different languages which are analyzed
>> > with the correct analyzer.
>> > We used the me
ywordTokenizer has similar behaviour. It injects a single token.
>> >
>> http://lucene.apache.org/core/3_0_3/api/all/org/apache/lucene/analysis/KeywordAnalyzer.html
>> >
>> > Ahmet
>> >
>> >
>> > On Wednesday, April 15, 2015 3:12 PM,
; > On Sunday, April 19, 2015 1:37 PM, Lisa Ziri wrote:
> > Hi,
> > I'm upgrading to lucene 5.1.0 from lucene 4.
> > In our index we have documents in different languages which are analyzed
> > with the correct analyzer.
> > We used the method addDocume
ferent languages which are analyzed
> with the correct analyzer.
> We used the method addDocument of IndexWriter giving the correct analyzer
> for every different document.
> Now I see that I can define the analyzer used by the IndexWriter only in
> the creation and I cannot switch ana
h are analyzed
with the correct analyzer.
We used the method addDocument of IndexWriter giving the correct analyzer
for every different document.
Now I see that I can define the analyzer used by the IndexWriter only in
the creation and I cannot switch analyzer on the same IndexWriter.
We allow to do
Hi,
I'm upgrading to lucene 5.1.0 from lucene 4.
In our index we have documents in different languages which are analyzed
with the correct analyzer.
We used the method addDocument of IndexWriter giving the correct analyzer
for every different document.
Now I see that I can define the analyzer
I am doing. At the moment, to index a document, I
> break
> > it to sentences, and each sentence is analyzed (lemmatizing, stopword
> > removal etc.)
> > Now, what I am looking for is a way to create an analyzer (a class which
> > extends lucene's analyzer). This analyzer
r the reply,
> That's exactly what I am doing. At the moment, to index a document, I break
> it to sentences, and each sentence is analyzed (lemmatizing, stopword
> removal etc.)
> Now, what I am looking for is a way to create an analyzer (a class which
> extends lucene'
pword
removal etc.)
Now, what I am looking for is a way to create an analyzer (a class which
extends lucene's analyzer). This analyzer will be used for index and query
processing. It (a like the english analyzer) will receive the text and
produce tokens.
The Api of Analyzer requires implem
nk you for the reply,
> That's exactly what I am doing. At the moment, to index a document, I break
> it to sentences, and each sentence is analyzed (lemmatizing, stopword
> removal etc.)
> Now, what I am looking for is a way to create an analyzer (a class which
> extends lucene&
Hi Ahment,
Thank you for the reply,
That's exactly what I am doing. At the moment, to index a document, I break
it to sentences, and each sentence is analyzed (lemmatizing, stopword
removal etc.)
Now, what I am looking for is a way to create an analyzer (a class which
extends lucene'
like to create a text dependent analyzer.
That is, *given a string*, the analyzer will:
1. Read the entire text and break it into sentences.
2. Each sentence will then be tokenized, possesive removal, lowercased,
mark terms and stemmed.
The second part is essentially what happens in english
Hi
I would like to create a text dependent analyzer.
That is, *given a string*, the analyzer will:
1. Read the entire text and break it into sentences.
2. Each sentence will then be tokenized, possesive removal, lowercased,
mark terms and stemmed.
The second part is essentially what happens in
eam ts = analyzer().tokenStream("field", new StringReader(text))) {
final CharTermAttribute termAtt = ts.addAttribute(CharTermAttribute.class);
ts.reset(); // Resets this stream to the beginning. (Required)
while (ts.incrementToken())
list.add(termAtt.toString());
ts.end(); // Perfo
Hi all,
an Analyzer has access to content on a per-field level by overwriting
this method:
protected TokenStreamComponents createComponents(String fieldName,
Reader reader);
Is it possible to get to the document? I want to collect the text
content from the entire document within my
Hi,
I have a legacy problem with the token stream. In my application I create a
batch of documents from a unique analyzer (this due to configuration). I add
the field using the tokenStream from the analyzer(for internal reasons). In a
pseudo code this translates in :
Analyzer analyzer
he user. Does this invariant
still matter in this case?
I could see adjusting offsets in an analyzer. However, I feel like offsets
are a bit sacrosanct -- they refer to a character offset in the original
document -- not the result of analysis. Am I wrong in feeling this way?
So I question why
.java:1537)
at org.apache.lucene.index.IndexWriter.addDocument(IndexWriter.java:1207)
at org.apache.lucene.index.IndexWriter.addDocument(IndexWriter.java:1188)
When I use the "PerFieldAnalyzerWrapper" only with the analyzer as default
analyzer:
this.analyzer = new Per
Christoph Kaser <
christoph.ka...@iconparc.de> wrote:
> Hello Milind,
>
> if you don't set the field to be tokenized, no analyzer will be used and
> the field's contents will be stored "as-is", i.e. case sensitive.
> It's the analyzer's job to toke
: Re: Can't get case insensitive keyword analyzer to work
Hello Milind,
if you don't set the field to be tokenized, no analyzer will be used and
the field's contents will be stored "as-is", i.e. case sensitive.
It's the analyzer's job to tokenize the input, so i
Hello Milind,
if you don't set the field to be tokenized, no analyzer will be used and
the field's contents will be stored "as-is", i.e. case sensitive.
It's the analyzer's job to tokenize the input, so if you use an analyzer
that does not separate the input
9, 2014 at 4:39 PM, Milind wrote:
>
>> I looked at a couple of examples on how to get keyword analyzer to be
>> case insensitive but I think I missed something since it's not working for
>> me.
>>
>> In the code below, I'm indexing text in upper case and s
g 9, 2014 at 4:39 PM, Milind wrote:
> I looked at a couple of examples on how to get keyword analyzer to be case
> insensitive but I think I missed something since it's not working for me.
>
> In the code below, I'm indexing text in upper case and searching in lower
> case. Bu
I looked at a couple of examples on how to get keyword analyzer to be case
insensitive but I think I missed something since it's not working for me.
In the code below, I'm indexing text in upper case and searching in lower
case. But I get back no hits. Do I need to something more whil
Sent from my BlackBerry® smartphone
-Original Message-
From: Cemo
Date: Thu, 31 Jul 2014 11:04:18
To:
Reply-To: java-user@lucene.apache.org
Subject: usage of CollationAttributeFactory StandardTokenizer Analyzer
Hi,
I am trying to use CollationAttributeFactory with a custom analyzer
Hi,
I am trying to use CollationAttributeFactory with a custom analyzer. I am
using StandardTokenizer with CollationAttributeFactory as in
org.apache.lucene.collation.CollationKeyAnalyzer.
protected TokenStreamComponents createComponents(String fieldName
Thanks again Steve. It was the version number. I hadn't noticed the
deprecated warning. Changing to use Version.LUCENE_47 fixed the problem.
On Wed, Jul 23, 2014 at 8:20 PM, Steve Rowe wrote:
> On Jul 23, 2014, at 7:43 PM, Milind wrote:
>
> >>> input=esl2.gbr
> >>> output=[esl2.gb][r]
On Jul 23, 2014, at 7:43 PM, Milind wrote:
>>> input=esl2.gbr
>>> output=[esl2.gb][r]
>>>
>>> This is a bug, which was fixed in Lucene 4.7 - see <
> https://issues.apache.org/jira/browse/LUCENE-5391>
>
> BTW, I changed the POM dependency to 4.7.1, but I'm still seeing the same
> output. I
1 - 100 of 778 matches
Mail list logo
