Storing the data in the index, mainly for non-structured data.
We plan to implement something like this ThingDB from http://
demo.openlibrary.org/about/tech, and though that maybe lucene +
JdbcDirectory could act as a backend.
gui
On Sep 3, 2007, at 2:34 PM, Askar Zaidi wrote:
Yes. Every ti
Yes. Every time a user updates a piece of information, you do the update in
the DB as well as the Index. If you are using Hibernate, they have an API
that does this mapping. I am not sure why you plan to store data in the
Index ?? Storing data is the DBs job, searching is the Index job. I would
sug
1) I don't understand why the index would get corrupted. We store
huge data
and meta-data using Lucene.
I got that information when lucene 1.4 was the lastest version, may
have changed. I'll trust you.
2) For this, I synced Lucene with the DB operations. If you use
Hibernate,
theres an A
1) I don't understand why the index would get corrupted. We store huge data
and meta-data using Lucene.
2) For this, I synced Lucene with the DB operations. If you use Hibernate,
theres an API for that. Or, you could just write your own factory methods to
add/delete/edit index documents when a DB o