son <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Sunday, 8 October, 2006 8:33:59 PM
Subject: Re: lucene link database
A quick word of caution about doc IDs. Lucene assigns a document id at index
time, but that ID is *not* guaranteed to remain the same for a given
document. For instance...
A quick word of caution about doc IDs. Lucene assigns a document id at index
time, but that ID is *not* guaranteed to remain the same for a given
document. For instance... you index docs A, B, and C. They get Lucene IDs 1,
2, 3. Then you remove doc B and optimize the index. As I understand it, doc
Like Erick said, one Lucene Document usually doens't equal to one
table entry. You need to flatten the database object into Lucene
Document. You can write your code in Hibernate and use Compass to
store data into Lucene. If you code is already finished, or you want a
scalable solution, DBSight can
Dear Erick;
Thank you for your detailed insight. I have been trying to code a graph
object database for sometime.
I have prototyped on relational as well as object oriented databases,
including opensource and commercial implementations.
(so far, I have tried hibernate, objectivity/db, db4o) whi
Aproach it in whatever way you want as long as it solves your problem .
My first question is why use lucene? Would a database suit your needs
better? Of course, I can't say. Lucene shines at full-text searching, so
it's a closer call if you aren't searching on parts of text. By that I mean
that i
Hello,
I would like to make a link database using lucene. Similar to one that
nutch uses. I have read the basic documentation and understood how
document indexing, search, and scoring works. But what I like is
different documents having different kind of links (semantic links) to
each other.
