Hi Gert,

 

This appears to be fixed now.  The problem was indeed that the name of my solr field was pid, not PID.  Thanks much for the help.

 

This behavior is surprising to me though, as I had updated the demoFoxmlToSolr.xslt file to use pid in place of PID for the solr field name attribute.  Does using GSearch with Solr require the Solr schema to include a field named PID even if the xslt has been updated?

 

Best,

Rob

 

 

From: Gert Schmeltz Pedersen [mailto:gsp@dtic.dtu.dk]
Sent: Thursday, December 09, 2010 11:32 AM
To: Support and info exchange list for Fedora users.
Subject: Re: [fcrepo-user] Gsearch/Solr indexing problem

 

Hi Robert,

 

The required field name is PID, not pid.

 

The URL is <fgsindex.indexBase>/update, you can see that in the code, it is not written to the gsearch log, maybe it is in the solr log. The data that is posted is in the gsearch log, after indexDoc=

 

Cheers,

Gert

 

 

On 09/12/2010, at 16.06, Wolff, Robert wrote:



Hi Gert,

 

fgsindex.indexBase is set to http://localhost:8080/solr, which is correct.  I’ve retried indexing after adding the additional lucene library, but still have the same problem. 

 

I’ve attached the relevant portion of the GSearch log when attempting to index demo:SmileyBucket using updateIndex fromPid.  It only seems to indicate that nothing was indexed.  Is there something I’m not seeing?  I should note that the solr index was empty when I ran this.

 

Also, is it possible to see exactly what URL GSearch is using to post to solr?

 

Thanks,

Rob

 

 

From: Gert Schmeltz Pedersen [mailto:gsp@dtic.dtu.dk] 
Sent: Wednesday, December 08, 2010 4:08 AM
To: Support and info exchange list for Fedora users.
Subject: Re: [fcrepo-user] Gsearch/Solr indexing problem

 

Hi Robert,

 

There are three properties in index.properties that make GSearch and Solr work together, fgsindex.operationsImpl, fgsindex.indexBase, and fgsindex.indexDir. Especially, indexBase seems to be wrong in your case, please check, and the GSearch log should have more info near where you found the Solr documents. Solr 1.4.1 should be ok, but you should add lucene-memory-2.9.3.jar as part of the transition from solr 1.3.

 

Best,

Gert

 

 

On 07/12/2010, at 23.26, Wolff, Robert wrote:




Hi Everyone,

 

I’m using GSearch 2.2 with Solr 1.4.1.  (If it helps anyone, to do this I updated three libraries in fedoragsearch/WEB-INF/lib: lucene-core-2.9.3,jar, lucene-demos-2.9.3.jar, and lucene-highlights-2.9.3.jar.)

 

My problem right now is that I can’t index anything in Solr using GSearch.  When I use updateIndex, either fromFoxmlFiles or fromPid, the Solr log doesn’t indicate that the /update handler was used and the documents are not indexed.  I’ve made sure to send a commit directive manually after trying to index.

 

I can take the Solr documents found in the GSearch log file and post them manually via curl without any problem, so the results of the xslt transform are valid.  And once they’re in, I can access the index via browseIndex and gfindObjects in GSearch.

 

I’m stumped.  Why would I be able to post them myself but GSearch not be able to?  Could it be related to using Solr 1.4.1?

 

Thanks for any help.

 

Cheers,

Rob

 

 

Robert Wolff

University of New Hampshire Library

 

 

<ATT00001.c><ATT00002.c>

 

<fedoragsearch.log><ATT00001.c><ATT00002.c>