On Thursday 03 April 2008 08:08:09 Dominique Béjean wrote:
> Hum, it looks like it is not true.
> Use a do-while loop make the first terms.term().field() generate a null
> pointer exception.
Depends which terms method you use.
TermEnum terms = reader.terms();
System.out.println(terms.term
Hi Bruce,
On 04/02/2008 at 4:58 PM, [EMAIL PROTECTED] wrote:
> I am having a problem when searching for certain Unicode
> characters, such as the Registered Trademark. That's the
> Unicode character 00AE. It's also a problem searching for a
> Japanese Yen symbol (Unicode character 00A5).
>
> I'm
Hum, it looks like it is not true.
Use a do-while loop make the first terms.term().field() generate a null
pointer exception.
-Message d'origine-
De : Daniel Noll [mailto:[EMAIL PROTECTED]
Envoyé : mardi 1 avril 2008 23:58
À : java-user@lucene.apache.org
Objet : Re: Problems about using L
I am having a problem when searching for certain Unicode characters, such as
the Registered Trademark. That's the Unicode character 00AE. It's also a
problem searching for a Japanese Yen symbol (Unicode character 00A5).
I'm using the Lucene 2.0.0 jar file, and we used to use Lucene 1.4.2 jar fi
Nitasha Walia (niwalia) wrote:
Hi,
I am a new user of Java Lucene and need to learn how to add a new
attribute, such that, given a database of emails, containing sender
information, searching for a keyword, results in
what kind of database do you use to store your emails?
I am asking bec
Try
http://www.nabble.com/Lucene---Java-Users-f45.html
Updating may not be as easy as you think. You'll be
changing your index *every* time a user accesses it. And your
changes won't be seen until you close/reopen the searcher.
But maybe you've worked it out already
Erick
On Wed, Apr 2, 20
This is "fast and loose" code (from my head; check the syntax). I *highly*
recommend you get a copy of the book Lucene in Action; it will really
help.
To create the index, add a document with two fields; one for the sender
and one for the email text.
IndexWriter indexWriter = new IndexWriter(.
Updating index is easy, I can have a background thread to do it.
Someone mentioned the "searchable archive" before, where do I find it?
Thanks,
-Original Message-
From: Erick Erickson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 02, 2008 11:12 AM
To: java-user@lucene.apache.org
Subj
Hi,
I am a new user of Java Lucene and need to learn how to add a new
attribute, such that, given a database of emails, containing sender
information, searching for a keyword, results in
1. The sender of the email
2. The email.
I am using Lucene-2.3.1, and don't know where to start in the hu
The problem here is that you'll have to keep deleting and
adding your documents in order to update the counter field for
all of these solutions, and I doubt that's what you really want
to do. There is much discussion of updating a document that's
already in the index, but I don't think it's there y
wuqi wrote:
Thank you Karl. I am just interested in how does Luke reconstruct
with field that is unsorted and has no TermVector. Seems Luke have to
iterate all the terms in the index,and check whether certain term is
contained in the document.
Correct, that's exactly how this function works in
I'm trying to figure out what the best practice is in term of using sorting
or customized scoring.
For example, if I have want to index some static pages and rank them by how
many times a page is viewed. I can get the page view counters and store
them in the index document as a field COUNTER. I
Thank you Karl.
I am just interested in how does Luke reconstruct with field that is unsorted
and has no TermVector. Seems Luke have to iterate all the terms in the
index,and check whether certain term is contained in the document.
- Original Message -
From: "Karl Wettin" <[EMAIL PROT
wuqi skrev:
> Hi,
>
> I want to reconstruct the field value from index, just the same as the
> function "Reconstruct and Edit" in the tool "Luke" . Just any hints is OK.
> Thanks in advance.
>
> Thanks
> -qi
http://issues.apache.org/jira/browse/LUCENE-1016
karl
---
the example you have sent is too small for the type of compression implemented
in lucene. The problem is that you have to store decoding symbol table , header
...* for each* document you compress.
The best you can do for this would be to use some compressor with static
decoding table (some ent
This has been discussed many times on the list. If you go to the searchable
version of the mailing list, you'll find a wealth of information on this
topic much
more quickly..
Best
Erick
On Wed, Apr 2, 2008 at 7:03 AM, wuqi <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I want to reconstruct the field valu
It's generally considered best practice to compress things first in
your app and then add them as a binary field. That being said, I
don't see why that would blow up on it's own. Have you tried
compressing it outside of Lucene to see what happens? If you can
reproduce it as a test case
Wojtek H a écrit :
Hi all,
Snowball stemmers are part of Lucene, but for few languages only. We
have documents in various languages and so need stemmers for many
languages (in particular polish). One of the ideas is to use ispell
dictionaries. There are ispell dicts for many languages and so thi
Hi,
I want to reconstruct the field value from index, just the same as the function
"Reconstruct and Edit" in the tool "Luke" . Just any hints is OK. Thanks in
advance.
Thanks
-qi
And I just found an old jira issue which might explain this behavior
LUCENE-533
http://www.archivum.info/[EMAIL PROTECTED]/2006-03/msg00265.html
Cedric
On Wed, Apr 2, 2008 at 3:15 PM, Cedric Ho <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> It seems that SpanNearQuery doesn't consider the boosting o
Hi all,
It seems that SpanNearQuery doesn't consider the boosting of the nested terms:
1.334 = (MATCH) weight(spanNear([content2MBM:morgan^4.0,
content2MBM:stanley^4.0], 2, true) in 11976), product of:
2.0 = queryWeight(spanNear([content2MBM:morgan^4.0,
content2MBM:stanley^4.0], 2, true
21 matches
Mail list logo