Hi Peri

What do the warnings say?

What happens if you updateIndex fromPid?

Gert


On 13/12/2013, at 19.42, Peri Stracchino wrote:

> Hi 
> We've been running fedoragsearch 2.5 for quite a while against solr 1.4. We 
> want to upgrade it to run against solr 3.6.1.
> Now my solr 3.6.1 installation seems to be working ok - I can post and index 
> the demonstration xml files. I can also see these files if I go to gsearch 
> browseIndex and give *:* as my start term, so its obviously looking in the 
> right place for the index.
> 
>  But its not working properly against my new solr yet, because when I try to 
> update index from foxml files, it runs then finishes with no documents 
> indexed, just warnings
> 
> I'v changed SOLR_HOME to the new solr 
> I have copied the schema.xml and solrconfig.xml from <SOLR_HOME>/conf into  
> fedoragsearch/WEB-INF/classes/fgsconfigFinal/<our index name>/conf.  the 
> foxml to solr indexing format xslt transformation document we were using with 
> the old solr version is still present.
> fgsindex.indexBase    = http://<our server address>/solr
> fgsindex.indexBase    =<oursolr_home>/data/index
> 
> It must surely be looking in the right place for the foxml files, because 1) 
> the fedora installation hasnt changed, and 2) its reporting an appropriate 
> number of warnings, given the number of objects in the system and that each 
> one has apparently failed. If I run uopdate index create empty it makes the 
> usual request to manualy stop solr, clear the index and restart solr, when I 
> run updateindex from foxml it initially starts without complaint - its only 
> when it finishes that it emerges that nothing has actually indexed
> 
> Is there some critical gsearch reconfiguration step I'v missed out, or can 
> anyone suggest any useful way I can diagnose whats going wrong? I suspect 
> perhaps there is something in the foxml files - or the output produced by the 
> transformation script - which conflicts with the schema.xml - it this seems 
> like the most likely scenario then I'll continue testing this line by line, 
> but I'm concerned I may be looking in the wrong direction
> 
> any pointers would be much appreciated! 
> 
> Peri
> 
> 
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT 
> organizations don't have a clear picture of how application performance 
> affects their revenue. With AppDynamics, you get 100% visibility into your 
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk_______________________________________________
> Fedora-commons-users mailing list
> Fedora-commons-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/fedora-commons-users


------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Fedora-commons-users mailing list
Fedora-commons-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users

Reply via email to