Well, I admit I'm not really clear on the big picture, but it looks to me as if the problem is in SolrServiceImpl.java in writeDocument(). The clause that calls the solr extract handler does not seem to add any of the record metadata without prepending 'literal.' to it -- specifically search.uniqueid!
If you ignore that section of code -- for instance if you dumbly substitute the line if(false&&CollectionUtils.isNotEmpty(streams)) for the original test on line 692, everything proceeds normally. This is an addition since v4.1, and again, I'm not sure what is supposed to be accomplished here but it doesn't seem to be working quite right. Any comments from the author(s)? Cheers! Bill On Mon, Sep 8, 2014 at 2:28 PM, Hilton Gibson <[email protected]> wrote: > Hi All > > Assuming these are linux systems, then check folder and file permissions for > the SOLR service. > Then check the config file for correct use. > See: http://wiki.lib.sun.ac.za/index.php/SUNScholar/SOLR_Discovery > Then update the indexes. > > Cheers > > hg > > > Hilton Gibson > Ubuntu Linux Systems Administrator > JS Gericke Library > Room 1025C > Stellenbosch University > Private Bag X5036 > Stellenbosch > 7599 > South Africa > > Tel: +27 21 808 4100 | Cell: +27 84 646 4758 > > > On 8 September 2014 20:08, Bill Tantzen <[email protected]> wrote: >> >> For what it's worth, after a similar update I am seeing exactly the >> same error with about 98% of my records. Anybody else seeing this >> problem? Did I miss an upgrade step? >> >> Cheers, >> Bill >> >> On Tue, Aug 12, 2014 at 12:40 PM, Ed Goulet <[email protected]> wrote: >> > Hi All, >> > >> > Recently upgraded from 4.1 to 4.2 >> > >> > I have some collections that now show less items than they used to ... >> > some show no items now :-( >> > >> > Example: suppose the collection's handle is 123456789/400 and items >> > within are 401 to 404. Used to show all 4 items when viewing the >> > collection's webpage. Now might only show 1 item, or none. If I >> > explicitly type in the 401 through 404 handle URL, then I see each item, >> > so they do still exist. >> > >> > Possibly related, I am having difficulties running "dspace >> > index-discovery" as it throws the following exceptions: >> > >> > ERROR org.dspace.discovery.SolrServiceImpl @ Error while writing item to >> > discovery index: 123456789/22 message:Document is missing mandatory >> > uniqueKey field: search.uniqueid >> > >> > Ideas? >> > >> > tia, >> > >> > Ed >> > >> > >> > ------------------------------------------------------------------------------ >> > _______________________________________________ >> > DSpace-tech mailing list >> > [email protected] >> > https://lists.sourceforge.net/lists/listinfo/dspace-tech >> > List Etiquette: >> > https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette >> >> >> ------------------------------------------------------------------------------ >> Want excitement? >> Manually upgrade your production database. >> When you want reliability, choose Perforce >> Perforce version control. Predictably reliable. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk >> _______________________________________________ >> DSpace-tech mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/dspace-tech >> List Etiquette: >> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette > > ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
