What about job deletion document cleanup, etc? Overlapping job runs using the same output connection? We've had this discussion before; the connector can certainly have hooks added but unless you intend to construct some kind of data structure on the Solr end that tries to keep track of all that, you're likely not going to get quite what you are looking for.
Karl From: ext Jack Krupansky [mailto:[email protected]] Sent: Wednesday, June 02, 2010 10:15 AM To: [email protected] Subject: Re: Setting up Solr 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: [email protected]<mailto:[email protected]> Sent: Wednesday, June 02, 2010 9:09 AM To: [email protected]<mailto:[email protected]> 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 [email protected]<mailto:[email protected]> [mailto:[email protected]] Sent: Wednesday, June 02, 2010 9:08 AM To: [email protected]<mailto:[email protected]> 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 [email protected]<mailto:[email protected]> From: [email protected] [mailto:[email protected]] Sent: Wednesday, June 02, 2010 6:32 PM To: [email protected] 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 [email protected] [mailto:[email protected]] Sent: Wednesday, June 02, 2010 9:00 AM To: [email protected] 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 [email protected]<mailto:[email protected]> From: Jack Krupansky [mailto:[email protected]] Sent: Wednesday, June 02, 2010 4:42 PM To: [email protected] 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: [email protected]<mailto:[email protected]> Sent: Wednesday, June 02, 2010 1:46 AM To: [email protected]<mailto:[email protected]> 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 [email protected]<mailto:[email protected]> 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.
