hehe, it is xmas, time to play fire.
Merry Christmas to Lucene!!
On Wed, Dec 24, 2008 at 9:59 PM, Erick Erickson wrote:
> You're really, really playing with fire here. Your document IDs may
> change, and in fact *will* change if you delete a document and
> then optimize. Say you index 100 d
Hello Mark,
As of the moment the index could not be rebuilt to remove norms.
Right now, I'm trying to figure out what luke is doing by going through source
code.
Using whatever settings I find, create a very small app just to do a bit of
search.
This small app has 1600 mb heapspace while luk
We don't know those norms are "the" problem. Luke is loading norms if
its searching that index. But what else is Luke doing? What else is your
App doing? I suspect your app requires more RAM than Luke? How much RAM
do you have and much are you allocating to the JVM?
The norms are not necessari
You're really, really playing with fire here. Your document IDs may
change, and in fact *will* change if you delete a document and
then optimize. Say you index 100 docs, delete number 50 and
optimize. Documents that originally had IDs 51-100 will now have
IDs 50-99 and your hierarchy will be messed
I am building up an index with documents that are hierarchical in their
relationship to each other. After I insert a Document into the index, how do
I know its document ID? I need that to pass to the next document as the
"ParentID"
Ian
Is there away to not factor in norms data in scoring somehow?
I'm just stumped as to how Luke is able to do a seach (with limit) on the docs
but in my code it just dies with OutOfMemory errors.
How does Luke not allocate these norms?
From: Mark Miller
To: jav
Hi Aleks
Yep, sorry think I was at wrong window :) .. I really have got things solved
now.
Thanks
-Amar
On Wed, Dec 24, 2008 at 3:37 PM, Aleksander M. Stensby <
aleksander.sten...@integrasco.no> wrote:
> Hello Amar,
> the reason why people got confused from your questions is that you are
> usin
Hello Amar,
the reason why people got confused from your questions is that you are
using Hibernate Search (which is built on top of Lucene and Hibernate) to
persist objects from your DB to lucene. So, you should really ask such
questions on the hibernate mailing list since the indexing logic
Hello Erick,
ah I got the problem solved :). here is how I changed my recipe object to be
class Recipe {
@DocumentId
Integer id;
@Field(index = Index.TOKENIZED, name="chainName")
@FieldBridge(impl= ChainFieldBridge.class)
Chain chain;
}
Here what I am trying to do is, save object to be as index
: a) once a doc is added to an index, it will not get modified/deleted
: b) all the fields added are keywords (mostly numbers) - no analysis is
: required.
: c) indexing speed is more important than querying speed.
: d) every document is the same - there is no boost or relevancy required.
:
: e
10 matches
Mail list logo