pass this my own Analyzer to WordnetSynonymParser
constructor then it works okay... except my WordNet enriched Lucene
index built with my WordNet-enabled Analyzer is spewing totally wrong
results...
Which Analyzer should I use to pass to WordnetSynonymParser constructor,
and does someo
g for a keyword analyzer.
>>
>> http://lucene.apache.org/java/3_0_2/api/core/org/apache/lucene/analysis/KeywordAnalyzer.html
>>
>> On Mon, May 30, 2011 at 8:48 PM, G.Long wrote:
>>
>> Hello :)
>>>
>>> I'm wondering which Analyzer would be the best to
) ?
Regards,
Le 30/05/2011 17:25, bmdakshinamur...@gmail.com a écrit :
I think you are looking for a keyword analyzer.
http://lucene.apache.org/java/3_0_2/api/core/org/apache/lucene/analysis/KeywordAnalyzer.html
On Mon, May 30, 2011 at 8:48 PM, G.Long wrote:
Hello :)
I'm wondering which Ana
I think you are looking for a keyword analyzer.
http://lucene.apache.org/java/3_0_2/api/core/org/apache/lucene/analysis/KeywordAnalyzer.html
On Mon, May 30, 2011 at 8:48 PM, G.Long wrote:
> Hello :)
>
> I'm wondering which Analyzer would be the best to query exact value for a
>
Hello :)
I'm wondering which Analyzer would be the best to query exact value for
a property. I read the javadoc and it it said that when a document is
indexed, I could use the Field.Index.NOT_ANALYZED to store the value as
is and then I would be able to query for it. But in the same ti
I don't think there's anything you can use out of the box, but if you
search for the mail thread (see serchable archives) for a thread
titled "Hebrew and Hindi analyzers" you might find something
useful.
Not much help I know, but perhaps a place to start.
And yes, you should use the same analyzer
Hi All,
I've been trying to index some non-english [Indian languages] in unicode
utf-8. For all these languages we don't have any stemmer or tokenizers etc.
To keep the searching simple I'ld like to be able to do exact word
searches/matches as a first step. I'ld like to know which will be the
simpl
OK, I will try it.
Thank you.
> -Original Message-
> From: Erick Erickson [mailto:[EMAIL PROTECTED]
> Sent: Freitag, 8. Februar 2008 14:25
> To: java-user@lucene.apache.org
> Subject: Re: Which analyzer
>
> WhitespaceAnalyzer should do the trick. Give it a try...
&
son [mailto:[EMAIL PROTECTED]
> > Sent: Freitag, 8. Februar 2008 00:20
> > To: java-user@lucene.apache.org
> > Subject: Re: Which analyzer
> >
> > *How* do you want to search them? If it's simply exact matches, then
> > WhitespaceAnalyzer should work fine.
> >
&g
o: java-user@lucene.apache.org
> Subject: Re: Which analyzer
>
> *How* do you want to search them? If it's simply exact matches, then
> WhitespaceAnalyzer should work fine.
>
> But if you want to, for example, look at date ranges or number
> ranges, you'll have to be more
*How* do you want to search them? If it's simply exact matches, then
WhitespaceAnalyzer should work fine.
But if you want to, for example, look at date ranges or number
ranges, you'll have to be more clever.
What do you want to accomplish?
Best
Erick
On Feb 7, 2008 3:25 PM, <[EMAIL PROTECTED]>
Hi,
I have a huge number of documents which contain mainly numbers and dates
(german format dd.MM.), like this:
Tgr. gilt ab 01.01.99 01.01.99 01.01.99 01.01.99 01.01.99 01.01.99
01.01.99 01.01.99 01.01.99 01.01.99 01.01.99 01.01.99 46X0 01
0480101080512070010
Gefahren
> You can answer an awful lot of this much faster than waiting
> for someone
> to reply by getting a copy of Luke and look at the parse results using
> various
> analyzers.
Ah cool, you mean the "explain structure" button.
> Try KeywordAnalyzer for your query.
>
> Combine queries programmatica
You can answer an awful lot of this much faster than waiting for someone
to reply by getting a copy of Luke and look at the parse results using
various
analyzers.
And you can use query.toString() to see the parsed results as well.
Try KeywordAnalyzer for your query.
Combine queries programmatica
> The caution to use the same analyzer at index and query time is,
> in my experience, simply good advice to follow until you are
> familiar enough with how Lucene uses analyzers to keep from
> getting really, really, really confused. Once you understand
> when analyzers are used and how they effec
> > How can I search for fields stored with Field.Index.UN_TOKENIZED?
>
> Use TermQuery.
>
> > Why do I need an analyzer for searching?
>
> Consider a full-text field that will be tokenized removing special
> characters and lowercased, and then a user querying for an uppercase
> word. The
I'm pretty sure that UN_TOKENIZED really bypasses analysis
entirely. so yes, it's a little confusing that you can specify an
analyzer but then pass a flag that says, in effect, "ignore the
analyzer I *said* I wanted to use".
So, in your example, you *are* running your query through
SimpleAnalyzer,
On Jan 13, 2008, at 12:08 PM, <[EMAIL PROTECTED]> wrote:
I have some doubts about Analyzer usage. I read that one shall
always use
the same analyzer for searching and indexing.
Why? How does the Analyzer effect the search process? What is
analyzed here
again?
As you surmised, it is becaus
Hi,
I have some doubts about Analyzer usage. I read that one shall always use
the same analyzer for searching and indexing.
Why? How does the Analyzer effect the search process? What is analyzed here
again?
I have tried this out. I used a SimpleAnalyzer for indexing with
Field.Store.YES and Field
Assuming that you are indexing these in different fields in your Lucene
document, you can use a PerFieldAnalyzerWrapper to use different analyzers
for each field. Be sure you carefully coordinate the analyzer you use for
indexing with the one you use for searching or your results will not be what
Hello All,
I m new to Lucene and want to know which anayzer to use for indexing the Text
and Numbers as well. But here is a problem.
I have a xml file which has text and numbers in values. I want to index
some(special) nodes value with [text and Numbers] but don't need all of the
nodes to come
You understood me right, Erik. Your solution is working well, thanks.
Venu
-Original Message-
From: Erik Hatcher [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 05, 2006 6:03 PM
To: java-user@lucene.apache.org
Subject: Re: Which Analyzer to use when searching on Keyword fields
Venu
Venu,
I presume you're asking about what Analyzer to use with QueryParser.
QueryParser analyzes all term text, but you can fake it for Keyword
(non-tokenized) fields by using PerFieldAnalyzerWrapper, specifying
the KeywordAnalyzer for the fields you indexed as such.
The KeywordAnalyzer c
Hi,
I am using lucene 1.4.3. Some of my fields are indexed as Keywords. I
also have subclassed Analyzer inorder to put stemming etc. I am not sure
if the input is tokenized when I am searching on keyword fields; I don't
want it to be. Do I need to have a special case in the overridden method
(Anal
24 matches
Mail list logo
