[ 
https://jira.duraspace.org/browse/DS-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21675#comment-21675
 ] 

Tim Donohue commented on DS-980:
--------------------------------

Mark, 

That makes sense.  I forgot about the custom DSpace LocalHostRestrictionFilter.

I'm going to look into whether 'dspace-solr-3.3.0.0' can really just be a war 
overlay of 'solr-3.3.0'.  It seems like that might be a better way of creating 
our own custom 'dspace-solr' (and keeping track of all the changes).  After 
performing a diff between dspace-solr and Apache's 'solr-3.3.0', it looks like 
our only customizations are the following:

* A custom DSpace 'LocalHostRestrictionFilter' class
* customized web.xml to call that custom filter

With such minimal changes to the default solr-3.3.0.war, it seems like it'd be 
easier to redo this via a war overlay.

I'm trying this out now -- if it fails then I'll just revert back to a full 
copy of everything in Solr 3.3.0, like in the current branch at: 
http://scm.dspace.org/svn/repo/modules/dspace-solr/branches/dspace-solr-parent-3.3.0.0
   But, if it succeeds, then we are not duplicating as much Solr webapp 
code/files, and it will make our future Solr updates that much easier.
                
> Upgraded solr & lucene to version 3.3.0
> ---------------------------------------
>
>                 Key: DS-980
>                 URL: https://jira.duraspace.org/browse/DS-980
>             Project: DSpace
>          Issue Type: Improvement
>          Components: Discovery, DSpace API, JSPUI, Solr, XMLUI
>    Affects Versions: 1.8.0
>            Reporter: Kevin Van de Velde
>            Assignee: Tim Donohue
>            Priority: Major
>         Attachments: Lucene_&_Solr_version_upgrade_to_3_3_0.patch
>
>
> Since DSpace is still using solr 1.4.x & lucene 2.9.3 I have created a patch 
> that will upgrade these to version 3.3.0 (Lucene & solr have received 
> matching version numbers).
> Since the dspace solr also requires a LocalHostRestrictionFilter I have 
> created a dspace-solr module with version 3.3.0.0 at the following location: 
> http://scm.dspace.org/svn/repo/modules/dspace-solr/branches/dspace-solr-parent-3.3.0.0
> Because of the new dspace-solr module a local installation of this module is 
> required to actually test the patch (once the patch has been tested this 
> module will need to be deployed).
> Also a thing to note, the solr upgrade just required updating the poms, but 
> for Lucene some code had to be rewritten some extra eyes on this wouldn't 
> hurt (although the tests I performed have been successful).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
Get a FREE DOWNLOAD! and learn more about uberSVN rich system, 
user administration capabilities and model configuration. Take 
the hassle out of deploying and managing Subversion and the 
tools developers use with it. 
http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to