It would be nice to have a "commit at end of job" option for the Solr output connector. Granted, commit policy can be a lot more complicated than that, but it is a simple use case that would facilitate initial evaluations of LCF with Solr.
 
Thinking further ahead, it would be very useful to have "job status notification" messages that could be sent to an app (say, a "/update/lcf-job-status" request handler) that would note start, end, abort, and periodic status of LCF jobs. Then the app could commit as it desires with respect to individual job completion and larger collections of jobs for different repositories. For example, an app might wait for all non-continuous jobs to complete before committing. That would be a more comprehensive longer-term solution for the commit problem, but the simple end-of-job commit option would be more user-friendly in the near-term.

-- Jack Krupansky

From: karl.wright@nokia.com
Sent: Wednesday, June 02, 2010 9:09 AM
To: connectors-user@incubator.apache.org
Subject: RE: Setting up Solr

Solr has autocommit functionality built in.  Google for it and you will find out how to configure it.

 

Karl

 

From: ext Rohan.GPatil@cognizant.com [mailto:Rohan.GPatil@cognizant.com]
Sent: Wednesday, June 02, 2010 9:08 AM
To: connectors-user@incubator.apache.org
Subject: RE: Setting up Solr

 

Why can we have a job for this ? else is there any other way ?? (Windows ? in linux there are cron jobs )

 

Thanks & Regards,

Rohan G Patil

Cognizant  Programmer Analyst Trainee,Bangalore || Mob # +91 9535577001

Rohan.GPatil@cognizant.com

 

From: karl.wright@nokia.com [mailto:karl.wright@nokia.com]
Sent: Wednesday, June 02, 2010 6:32 PM
To: connectors-user@incubator.apache.org
Subject: RE: Setting up Solr

 

You can send any argument you want by configuring the output connector.  However, the explicit commit on every post will slow down performance of your crawls.

 

Karl

 

From: ext Rohan.GPatil@cognizant.com [mailto:Rohan.GPatil@cognizant.com]
Sent: Wednesday, June 02, 2010 9:00 AM
To: connectors-user@incubator.apache.org
Subject: RE: Setting up Solr

 

Hi,

 

Yes that is where I was stuck up.. making an explicit commit..

 

Can I send the argument commit=true while configuring the Repo connector.

 

Thanks & Regards,

Rohan G Patil

Cognizant  Programmer Analyst Trainee,Bangalore || Mob # +91 9535577001

Rohan.GPatil@cognizant.com

 

From: Jack Krupansky [mailto:jack.krupansky@lucidimagination.com]
Sent: Wednesday, June 02, 2010 4:42 PM
To: connectors-user@incubator.apache.org
Subject: Re: Setting up Solr

 

A short Solr tutorial is here:

 

http://lucene.apache.org/solr/tutorial.html

After running an LCF job that uses a Solr output connection, be sure to manually force a Solr "commit", for example:

 

    cd .../apache-solr-1.4.0/example/exampledocs
    java -jar post.jar


-- Jack Krupansky

 

From: Rohan.GPatil@cognizant.com

Sent: Wednesday, June 02, 2010 1:46 AM

To: connectors-user@incubator.apache.org

Subject: Setting up Solr

 

Hi,

 

I am stuck at setting up the Solr server to be used with LCF.

 

I am new to Solr.

 

Thanks & Regards,

Rohan G Patil

Cognizant  Programmer Analyst Trainee,Bangalore || Mob # +91 9535577001

Rohan.GPatil@cognizant.com

 

This e-mail and any files transmitted with it are for the sole use of
the intended recipient(s) and may contain confidential and privileged
information.
If you are not the intended recipient, please contact the sender by
reply e-mail and destroy all copies of the original message.
Any unauthorized review, use, disclosure, dissemination, forwarding,
printing or copying of this email or any action taken in reliance on this
e-mail is strictly prohibited and may be unlawful.

 

This e-mail and any files transmitted with it are for the sole use of
the intended recipient(s) and may contain confidential and privileged
information.
If you are not the intended recipient, please contact the sender by
reply e-mail and destroy all copies of the original message.
Any unauthorized review, use, disclosure, dissemination, forwarding,
printing or copying of this email or any action taken in reliance on this
e-mail is strictly prohibited and may be unlawful.

 

This e-mail and any files transmitted with it are for the sole use of
the intended recipient(s) and may contain confidential and privileged
information.
If you are not the intended recipient, please contact the sender by
reply e-mail and destroy all copies of the original message.
Any unauthorized review, use, disclosure, dissemination, forwarding,
printing or copying of this email or any action taken in reliance on this
e-mail is strictly prohibited and may be unlawful.