try to allocate more memory to your searcher.
ex. java -mx1024m ...
kapilChhabra
On Tue, 2005-07-19 at 23:32, Kipping, Peter wrote:
> Hi,
>
> I rebuilt my index with only a few minor changes, and now when I search
> on it I get nothing but out of memory exceptions. I don't know what
> would cau
On Jul 21, 2005, at 8:53 AM, Riccardo Daviddi wrote:
it's possible to set an unique id (as keyword field) to a doc by
looking in the index? I mean, it's possible to look in the index and
know what is the last id (which is a keyword field) and then decide
for the new id to associate to the new i
Hi all,
I have a problem related to index size and deleting and optimizing. So
from reading various sources online, it seems as though the size of the
Lucene index should become no larger than half the size of the disk
since during optimization, the size of the index can ballon to double
the origi
yes I was wondering if I could "use" lucene before the db.
What you mean with GUID? About the digest, well it's a possibility but
considering I have to store my docs in a db I think the best is abort
this and first of all store in db the doc and assign the key as unique
id in the index.
On 7/21/05
On Jul 21, 2005, at 3:43 PM, Riccardo Daviddi wrote:
What I want to to is to assign a unique id to each doc I add to the
index.
I was wondering if there is a method to assign a unique id directly
looking in the index so after I could store my doc in a db with the
same id as key.
So first Luc
What I want to to is to assign a unique id to each doc I add to the index.
I was wondering if there is a method to assign a unique id directly
looking in the index so after I could store my doc in a db with the
same id as key.
On 7/21/05, Erik Hatcher <[EMAIL PROTECTED]> wrote:
> You could certai
I think maxDoc doesn't sole my problem at all.
Correct me if I am wrong: suppose I have 5 docs in my index, and I
wanto to add one new doc to the index. if I use the maxDoc as the new
unique id for that document I obtain 5 (the first free position,
considering it starts from 0). Now suppose I delet
You could certainly use IndexReader to get the last document in the
index and retrieve its ID, but why?
What use case do you have in mind for such id's? Do they have a non-
arbitrary meaning? Do your documents have nothing unique to identify
them already?
Erik
On Jul 21, 2005, at 1
Going the DB way may be safer.
But you could use IndexReader's maxDoc() method to use the other
approach:
http://lucene.apache.org/java/docs/api/org/apache/lucene/index/IndexReader.html#maxDoc()
Otis
--- Riccardo Daviddi <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> it's possible to set an unique id
Hi all,
it's possible to set an unique id (as keyword field) to a doc by
looking in the index? I mean, it's possible to look in the index and
know what is the last id (which is a keyword field) and then decide
for the new id to associate to the new indexed doc? Or it's better
store the doc in a db
I think it would be better in this case to not use QueryParser. It is
not designed for your situation.
Build the query using BooleanQuery instead.
Peter Gelderbloem
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comm
On Jul 21, 2005, at 5:09 AM, Karthik N S wrote:
Do you want term frequency across an individual document or the
entire
index?
Of course the Frequency will have to be across the entire index.
In such case How does Explanation be usefull (Since Explanation is per
document)
Explanation wou
Hi
Erik
Apologies..
>> Do you want term frequency across an individual document or the entire
index?
Of course the Frequency will have to be across the entire index.
In such case How does Explanation be usefull (Since Explanation is per
document)
Thx in advance
Karthik
-Origin
13 matches
Mail list logo