SOLVED!! Aha! Make sure to update solrconfig.xml to the version supplied by DSpace v4.2. There, the default param lowernames is commented out; I suspect the default value must be false. I think (although I can't find any documentation that says so specifically), that lowernames substitutes underscore for dot transforming search.uniqueid to search_uniqueid -- thus generating the exception. (The documentation states as much for the example: Content-Type becomes content_type).
At the very least, configure the ExtractingRequestHandler according to the DS v4.2 solrconfig! Anyway, this took care of the problem for me! Cheers, Bill On Tue, Sep 9, 2014 at 2:52 AM, helix84 <[email protected]> wrote: > On Mon, Sep 8, 2014 at 10:35 PM, Bill Tantzen <[email protected]> wrote: >> 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. > > Not an explanation, just more context - that change in 4.2 [1] is a > bug fix for [2]. You might try commenting there or filing a new issue > (since it was already confirmed by 2 people). > > [1] > https://github.com/DSpace/DSpace/blame/dspace-4.2/dspace-api/src/main/java/org/dspace/discovery/SolrServiceImpl.java#L692 > [2] https://jira.duraspace.org/browse/DS-1958 > > > Regards, > ~~helix84 > > Compulsory reading: DSpace Mailing 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
