Ernesto De Santis writes:
> Hi Erik
>
> Ok, in PrefixQuery cases, non analyze is right.
>
It creates the same problems.
'example*' should find 'example' but does not if 'example' is stemmed
to 'exampl' and you don't analyze the prefix query.
>
> You search "example" and obtain x results.
> You
hi erik,
i'm creating a blogger application, where the users
can create blogs, upload pictures and post comments
etc etc.
i'm storing all the information using mysql
database. i'm indexing the database contents and
searching on this index.i'm using lucene to implement
this feature.
i give
On Mar 31, 2005, at 11:44 AM, pashupathinath wrote:
is it possible to index using a predefined analyzer
and search using a custom analyzer ??
Yes, its perfectly fine to do so with the caveat that you end up
searching for the terms exactly as they were indexed.
I end up doing this in most applic
On Mar 31, 2005, at 12:26 PM, Ernesto De Santis wrote:
Hi Erik
Finally, my name spelled correctly. :))
Ok, in PrefixQuery cases, non analyze is right.
But you think that non analyze in WildcardQuery is right?
Do I think its right? That's just the way it is. Whether that is
right or not I don
On Mar 31, 2005, at 6:36 PM, Yagnesh Shah wrote:
try {
fis = new FileInputStream(f);
HTMLParser parser = new HTMLParser(fis);
// Add the tag-stripped contents as a Reader-valued Text field
so it will
// get tokenized and indexed.
// doc.add(new Field("contents", pa
Hi! Eric,
I have modified HTMLDocument.java try section to used
doc.add(Field.Text("contents", l)); I am able to compile with following warning
about depricated API. But I am still unable to see any value.
compile warning #
compile-demo:
[javac] Compiling 1 sourc
I did index new documents and they are fine. thanks for your help Eric.
-Original Message-
From: Erik Hatcher [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 31, 2005 5:20 PM
To: java-user@lucene.apache.org
Subject: Re: error when query contains numbers
On Mar 31, 2005, at 5:00 PM, Omar
On Mar 31, 2005, at 5:00 PM, Omar Didi wrote:
CyAnalyzer:
[year] [2005] [yahoo123]
the analyzer I am using doesn t discard numbers but I can t find them.
any ideas??
If that is the analyzer you are using for indexing and you are using a
tokenized field type then those tokens will be indexed
I have used luke to look inside the index and i haven't found any numbers
except for the fields that were indexed as keywords. i have used the
AnalyzerDemo class in LIA, I got the following output:
Analyzing "welcome to the year 2005 yahoo123"
WhitespaceAnalyzer:
[welcome] [to] [the] [year
It's as easy as replacing a Jar, if you are upgrading from a Lucene
version with compatible index format. Some versions changed the index
format. See
http://cvs.apache.org/viewcvs.cgi/*checkout*/jakarta-lucene/CHANGES.txt?rev=1.96.2.6
for index format change information.
If the index format chan
Hello,
For 1) you'll need to write your own Analyzer that knows that you want
to be able to search on "abc", "123", and probably "abc123".
WhitespaceAnalyzer just breaks input on spaces.
2) I think I answered that in the Lucene in Action forum.
Otis
--- pashupathinath <[EMAIL PROTECTED]> wrote
Hi Erik
Ok, in PrefixQuery cases, non analyze is right.
But you think that non analyze in WildcardQuery is right?
You search "example" and obtain x results.
You search "ex?mple" and don't obtain any result.
This is correct for you?
It is difficult to analyze wildcard queries in lucene code?
Ernesto
is it possible to index using a predefined analyzer
and search using a custom analyzer ??
i'm searching using the built in whitespace
analyser. the problem is when i'm searching for a part
of a string the search results are zero.
i'm using white space analyzer. for example if the
statement is
Wildcard terms simply are not analyzed. How could it be possible to do
this? What if I search for "a*" - how could you stem that?
Erik
On Mar 31, 2005, at 9:51 AM, Ernesto De Santis wrote:
Hi
I get an unexpected behavior when use wildcards in my queries.
I use a EnglishAnalyzer develope
Hi
I get an unexpected behavior when use wildcards in my queries.
I use a EnglishAnalyzer developed with SnowballAnalyzer. version 1.1_dev
from Lucene in Action lib.
Analysis case:
When use wildcards in the middle of one word, the word in not analyzed.
Examples:
QueryParser qp = new Qu
As suggested before, the real killer for performance
in Lucene is when you have to read a stored field. It
doesn't matter how small the one field you want is,
Lucene will read *all* fields for that document off
the disk. If you have a large "body" field that will
get read too when you try read the
16 matches
Mail list logo
