I'm not a particular fan of Hibernate, but that may just reflect my unfamiliarity.
The real question is should you have two separate systems that you tie together, Lucene as a search engine AND a database for "other stuff". My *strong* preference is to keep the number of moving parts to a minimum so I'd start by choosing one or the other. You almost certainly won't be able to get acceptable performance out of text-based searching using a database, so I'd go for the Lucene-based solution first and only add in a database (in whatever form) if you find yourself unable to do it all in Lucene. NOTE: you really have to take off your database hat to use lucene. All the stuff you reflexively want to do about normalizing data goes right out the window. You do NOT want to try to make Lucene do joins, for instance. Flatten the data even if you cringe at the data replication <G>... Search the user list for "database" and you'll find a lot of discussion... Best Erick On Thu, Oct 2, 2008 at 7:28 PM, Mathias P.W Nilsson <[EMAIL PROTECTED]>wrote: > > Oh, I forgot. > > Would you save the documents as index on the file system or use Hibernate > search with lucene? > -- > View this message in context: > http://www.nabble.com/Advise-for-Mediabase-with-Lucene-tp19787867p19789551.html > Sent from the Lucene - Java Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
