Fair point, and that's how my current solr-based project works. I'm
thinking I would like the other advantages of an XML db: the ability to
run xqueries, batch updates, etc., alongside the Lucene searching. And I
want them integrated under the hood in Solr so that people smarter than
me will maintain and optimize the connections. But I agree that this
approach will have to prove that the extra overhead is worth it.
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
Sent: Monday, November 27, 2006 3:55 PM
To: [log in to unmask]
Subject: Re: [CODE4LIB] code4lib lucene pre-conference
Binkley, Peter wrote:
>There would probably be a lot of optimizations you could do within Solr
>to help with this kind of thing. Art and I talked a little about this
>at the ILS symposium: why not nestle the XML db inside Solr alongside
>Lucene? Solr could then manage the indexing of the contents of the db,
>and augment your search results with data from the db: you could get
>full records as part of your search results without having to store
>them in the Lucene index.
At this point, why use a DB? Just store your records in your server
file system. It's fast and less applications to worry about
maintaining. If your search matches 5 records, just open those 5 files
on your server.
Good conversations ... getting excited for the conference already!