Another thing you could consider is that rather than meshing all this
data into a single index, logically break out the data you need for
searching into one index, and the data you need for display into another
index.
This is the technique we use here and its been wildly successful for us,
as compared to going directly into the database.
Our DB is structured for ease of data entry/annotation rather than for
the ease is display. So we use our display index to have standard
realized datafields that are pulled from various tables in the database.
So, when we search we include the unique key that each matched term
points to, and then use this unique key to pull out our display time
information.
Its worked pretty well for us, so its certianly a viable approach.
- Matt
agatone wrote:
Hi,
I asked this question already on "lucene-general" list but also got advised
to ask here too.
I'm working on a project that has big database in the background (some
tables have about 1500000 rows). We decided to use Lucene for "faster"
search. Our search works similar as all searches: you write search string,
get list of hits with detail link. But there is dilemma if we should store
more data into index than it's needed.
One side of developing team insists that we should use lucene index as
somekind of storage for data so when you get hit, you go onto details and
then again use lucene to find document that matches the selected ID and take
the data from Lucene index. So in the end you end with copying complete
database tables into the lucene index.
Other side insists on storing to index only data that is displayed directly
to the user when showing the search results list and needed for search
criteria. When you go onto details, you have the matching ID so you can
pickup that row from database by that ID rather than search it inside Lucene
index.
Can someone please describe drawbacks and advantages of both approaches.
Actually can someone write down what's the actual profit, where and when of
the Lucene itself in real production env.
IT would be great if there is anyone who could write his experience with
indexing and searching large amount of data.
Thank you
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
