On Dec 13, 2006, at 7:24 PM, Andrew Hughes wrote:
I realize that I'm posting LOTS of complicated questions and I
am probably just looking at the equivalent of a HTML indexing/
search implementation.
(sorry for the delay)
I'm doing something sorta relational in my Collex project - http:/
I think the last structure is good. The index should be structured
according to how you want to search it. If your needs changed, you
should simply have another index. One index for all is not really
good. Index is more of trading space for time, so duplication is not
really a concern.
The first
Thanks Erick,
I'll give a representation of the data structure that I am trying to
index (in xml). This represents a relational data structure. Because
all Place (ie Kazakhstan) Person's are grouped together eta
USA
U.S.A
US
You are right. Database usually is in 3NF, while lucene usually works
on an array of objects. Different database has different data model.
There are quite some efforts to crawl database, create the lucene
index, keep it in sync with the database, and rendering the search
results. If data model cha
Tell us more about the problem you are trying to solve. Lucene is designed
for large text searching, not relations. Trying to "index a data structure"
seems like mis-application of Lucene. Without some idea of what you are
trying to accomplish, any advice you get is irrelevant at best...
Best
Er
