Return-Path: Delivered-To: apmail-incubator-connectors-user-archive@minotaur.apache.org Received: (qmail 73720 invoked from network); 2 Jun 2010 14:15:21 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Jun 2010 14:15:21 -0000 Received: (qmail 75570 invoked by uid 500); 2 Jun 2010 14:15:20 -0000 Delivered-To: apmail-incubator-connectors-user-archive@incubator.apache.org Received: (qmail 75493 invoked by uid 500); 2 Jun 2010 14:15:20 -0000 Mailing-List: contact connectors-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: connectors-user@incubator.apache.org Delivered-To: mailing list connectors-user@incubator.apache.org Received: (qmail 75485 invoked by uid 99); 2 Jun 2010 14:15:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jun 2010 14:15:20 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jack.krupansky@lucidimagination.com designates 38.102.63.181 as permitted sender) Received: from [38.102.63.181] (HELO smtp-2.01.com) (38.102.63.181) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jun 2010 14:15:12 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp-2.01.com (Postfix) with ESMTP id 828371ADEE4 for ; Wed, 2 Jun 2010 09:14:51 -0500 (CDT) Received: from smtp-2.01.com ([127.0.0.1]) by localhost (smtp-2.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dk8zaIkvEMAU for ; Wed, 2 Jun 2010 09:14:51 -0500 (CDT) Received: by smtp-2.01.com (Postfix, from userid 99) id 640571ADFB6; Wed, 2 Jun 2010 09:14:51 -0500 (CDT) Received: from JackKrupansky (207-38-211-252.c3-0.nyr-ubr1.nyr.ny.cable.rcn.com [207.38.211.252]) by smtp-2.01.com (Postfix) with ESMTPSA id A488C1ADEE4 for ; Wed, 2 Jun 2010 09:14:50 -0500 (CDT) Message-ID: From: "Jack Krupansky" To: References: <1FC937CB0EFA4F0A894682D10ACD3A92@JackKrupansky> In-Reply-To: Subject: Re: Setting up Solr Date: Wed, 2 Jun 2010 10:14:47 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00C5_01CB023C.6DBBD230" X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8089.726 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726 X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. ------=_NextPart_000_00C5_01CB023C.6DBBD230 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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=20 Sent: Wednesday, June 02, 2010 9:09 AM To: connectors-user@incubator.apache.org=20 Subject: RE: Setting up Solr Solr has autocommit functionality built in. Google for it and you will = find out how to configure it. =20 Karl =20 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 =20 Why can we have a job for this ? else is there any other way ?? (Windows = ? in linux there are cron jobs ) =20 Thanks & Regards, Rohan G Patil Cognizant Programmer Analyst Trainee,Bangalore || Mob # +91 9535577001=20 Rohan.GPatil@cognizant.com =20 From: karl.wright@nokia.com [mailto:karl.wright@nokia.com]=20 Sent: Wednesday, June 02, 2010 6:32 PM To: connectors-user@incubator.apache.org Subject: RE: Setting up Solr =20 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. =20 Karl =20 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 =20 Hi, =20 Yes that is where I was stuck up.. making an explicit commit..=20 =20 Can I send the argument commit=3Dtrue while configuring the Repo = connector. =20 Thanks & Regards, Rohan G Patil Cognizant Programmer Analyst Trainee,Bangalore || Mob # +91 9535577001=20 Rohan.GPatil@cognizant.com =20 From: Jack Krupansky [mailto:jack.krupansky@lucidimagination.com]=20 Sent: Wednesday, June 02, 2010 4:42 PM To: connectors-user@incubator.apache.org Subject: Re: Setting up Solr =20 A short Solr tutorial is here: =20 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: =20 cd .../apache-solr-1.4.0/example/exampledocs java -jar post.jar -- Jack Krupansky =20 From: Rohan.GPatil@cognizant.com=20 Sent: Wednesday, June 02, 2010 1:46 AM To: connectors-user@incubator.apache.org=20 Subject: Setting up Solr =20 Hi, =20 I am stuck at setting up the Solr server to be used with LCF. =20 I am new to Solr. =20 Thanks & Regards, Rohan G Patil Cognizant Programmer Analyst Trainee,Bangalore || Mob # +91 9535577001=20 Rohan.GPatil@cognizant.com =20 This e-mail and any files transmitted with it are for the sole use = of=20 the intended recipient(s) and may contain confidential and = privileged=20 information. If you are not the intended recipient, please contact the sender = by=20 reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, = forwarding,=20 printing or copying of this email or any action taken in reliance = on this=20 e-mail is strictly prohibited and may be unlawful. =20 =20 This e-mail and any files transmitted with it are for the sole use = of=20 the intended recipient(s) and may contain confidential and = privileged=20 information. If you are not the intended recipient, please contact the sender = by=20 reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, = forwarding,=20 printing or copying of this email or any action taken in reliance = on this=20 e-mail is strictly prohibited and may be unlawful. =20 =20 This e-mail and any files transmitted with it are for the sole use = of=20 the intended recipient(s) and may contain confidential and = privileged=20 information. If you are not the intended recipient, please contact the sender = by=20 reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, = forwarding,=20 printing or copying of this email or any action taken in reliance = on this=20 e-mail is strictly prohibited and may be unlawful. =20 =20 ------=_NextPart_000_00C5_01CB023C.6DBBD230 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
It would be nice to have a "commit at end of = job" option=20 for the Solr output connector. Granted, commit policy can be a lot more=20 complicated than that, but it is a simple use case that would facilitate = initial=20 evaluations of LCF with Solr.
 
Thinking further ahead, it would be very = useful to have=20 "job status notification" messages that could be sent to an app (say, a=20 "/update/lcf-job-status" request handler) that would note start, end, = abort, and=20 periodic status of LCF jobs. Then the app could commit as it desires = with=20 respect to individual job completion and larger collections of jobs for=20 different repositories. For example, an app might wait for all = non-continuous=20 jobs to complete before committing. That would be a more comprehensive=20 longer-term solution for the commit problem, but the simple end-of-job = commit=20 option would be more user-friendly in the near-term.

-- Jack Krupansky

Sent: Wednesday, June 02, 2010 9:09 AM
Subject: RE: Setting up Solr

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

 

Karl

 

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

 

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

 

Thanks=20 & Regards,

Rohan=20 G Patil

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

Rohan.GPatil@cognizant.com=

 

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

 

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

 

Karl

 

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

 

Hi,

 

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

 

Can I send the = argument=20 commit=3Dtrue while configuring the Repo = connector.

 

Thanks=20 & Regards,

Rohan=20 G Patil

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

Rohan.GPatil@cognizant.com=

 

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

 

A short Solr = tutorial is=20 here:

 

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

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

 

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


-- Jack=20 Krupansky

 

From: Rohan.GPatil@cognizant.com= =20

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

To: connectors-user@incu= bator.apache.org=20

Subject: Setting = up=20 Solr

 

Hi,

 

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

 

I am new to Solr.

 

Thanks=20 & Regards,

Rohan=20 G Patil

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

Rohan.GPatil@cognizant.com=

 

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

 

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

 

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

 

------=_NextPart_000_00C5_01CB023C.6DBBD230--