lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Archambault" <>
Subject Re: Simple Faceted Searching out of the box
Date Fri, 22 Sep 2006 19:25:18 GMT
Okay, I'll use an example.

A recruitment (jobs) customer goes onto our website and posts an online job
posting to our newspaper website. Upon insert into the database, I need to
generate an xml file to be sent to SOLR to ADD as  a record to the search
engine. Same  goes for an edit, my database updates the record and then I
have to send an ADD statement to Solr again to commit my change. 2x the

I've been talking with other papers about Solr and I think what bothers many
is that there a is a deposit of information in a structured database here
[named A], then we have another set of basically the same data over here
[named B] and they don't understand why they have to manage to different
sets of data [A & B] that are virtually the same thing.  Many foresee a
maintenance nightmare. I've come to the conclusion that there's somewhat of
a disconnect between what a database does and what a search engine does. I
accept that the redundancy is necessary given the very different tasks that
each performs [keep in mind I'm still naive to the programming details here,
I understand conceptually].

In writing this to you another thought came to mind. Maybe there are
alternative ways to inject records into Solr outside the bounds of the
cygwin and CURL examples I've been using. Maybe that is the question we need
to be asking. What are some alternative ways to populate Solr?

Enough said, it's Friday afternoon.

Have a great weekend.


On 9/22/06, Erik Hatcher <> wrote:
> On Sep 22, 2006, at 2:45 PM, Tim Archambault wrote:
> > I believe there's a way to access MSSQL, MySQL etc. directly with
> > Lucene,
> > but not sure how to do this with SOLR.
> Nope.  Lucene is a pure search engine, with no hooks to databases, or
> document parsers, etc.  Lots of folks have built these kinds of
> things on top of Lucene, but the Lucene core is purely the text engine.
> How would you envision communicating with Solr with a database in the
> picture?   How would the entire database be initially indexed?  How
> would changes to the database trigger Solr updates?   I'm not quite
> clear on what it would mean for Solr to work with a database directly
> so I'm curious.
>         Erik

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message