hi Vijay, There are a few adavantages of using a handler over an ETL tool, 1) ETL tools are external and it needs its own setup ,configuration and management 2) They have their own custom syntax and learning curve 3) As they are external, there is an external network hop and additional xml marshalling/unmarshalling. So , do not expect the performance to be as good as the handler.
As to committing to solr, The patch provided does not make any changes to the existing Solr codebase. This is purely an addon . So you can very well drop in the jar to your existing solr installation and start working with. There are nly around 10-12 java files in the patch so you may not find it difficult comprehending the codebase. We are using it in production and our QA department does the necessary testing. But , if you encounter some problems please report back and we will be only glad to fix it and contribute back You can feel confident in using this even before it officially becomes a part of solr. Or if there is enough interest , we can consider hosting it in some other place (google code, sourceforge) for the benefit of the larger audience. --Noble On Feb 18, 2008 11:25 PM, Vijay Rao <[EMAIL PROTECTED]> wrote: > hi, > We have a similar requirement in our organization.We are planning to use > an > ETL tool to synchronize our DB with Solr. Looks like this is a better > approach. > Is it production quality? > When do you plan to commit this to Solr? > Cheers > Vijay > > > > On Feb 18, 2008 11:20 PM, Noble Paul (JIRA) <[EMAIL PROTECTED]> wrote: > > > > > [ > > > https://issues.apache.org/jira/browse/SOLR-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569979#action_12569979 > ] > > > > Noble Paul commented on SOLR-469: > > --------------------------------- > > > > Add a facility to delete documents from Solr index on the basis of a > solr > > query. > > It is useful if you wish to expire the documents after a certain period > of > > time. > > > > > > > DB Import RequestHandler > > > ------------------------ > > > > > > Key: SOLR-469 > > > URL: https://issues.apache.org/jira/browse/SOLR-469 > > > Project: Solr > > > Issue Type: New Feature > > > Components: update > > > Affects Versions: 1.3 > > > Reporter: Noble Paul > > > Priority: Minor > > > Fix For: 1.3 > > > > > > Attachments: SOLR-469.patch, SOLR-469.patch, SOLR-469.patch > > > > > > > > > We need a RequestHandler Which can import data from a DB or other > > dataSources into the Solr index .Think of it as an advanced form of > > SqlUpload Plugin (SOLR-103). > > > The way it works is as follows. > > > * Provide a configuration file (xml) to the Handler which takes in > > the necessary SQL queries and mappings to a solr schema > > > - It also takes in a properties file for the data source > > configuraution > > > * Given the configuration it can also generate the solr schema.xml > > > * It is registered as a RequestHandler which can take two commands > > do-full-import, do-delta-import > > > - do-full-import - dumps all the data from the Database > into > > the index (based on the SQL query in configuration) > > > - do-delta-import - dumps all the data that has changed > since > > last import. (We assume a modified-timestamp column in tables) > > > * It provides a admin page > > > - where we can schedule it to be run automatically at > regular > > intervals > > > - It shows the status of the Handler (idle, full-import, > > delta-import) > > > > -- > > This message is automatically generated by JIRA. > > - > > You can reply to this email to add a comment to the issue online. > > > > > -- --Noble Paul
