[
https://jira.duraspace.org/browse/DS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue closed DS-987.
--------------------------
Documentation Status: Complete or Committed (was: Needed)
Resolution: Fixed
Marking this as fixed (as noted above, the code fix actually came in DS-990).
I've also documented this change & added a small warning about usage of "ant
-Doverwrite=false update" to both these pages:
* https://wiki.duraspace.org/display/DSPACE/DSpace+Release+1.8.0+Notes
* https://wiki.duraspace.org/display/DSDOCDEV/Upgrading+a+DSpace+Installation
> By default, Solr Schemas & Configs don't upgrade properly & may cause
> instability
> ---------------------------------------------------------------------------------
>
> Key: DS-987
> URL: https://jira.duraspace.org/browse/DS-987
> Project: DSpace
> Issue Type: Bug
> Components: Solr
> Affects Versions: 1.7.0, 1.7.1, 1.7.2
> Environment: Any environment
> Reporter: Tim Donohue
> Assignee: Tim Donohue
> Priority: Major
> Fix For: 1.8.0
>
>
> By default, if users run simply 'ant update' to upgrade a DSpace instance,
> the Solr Configurations & Schemas will NOT upgrade properly. (Note: However,
> if you run 'ant -Doverwrite=true update', then Solr will upgrade properly)
> The reason, is that DSpace's Solr directory updates it configurations similar
> to the [dspace]/config/ directory.
> So, if you simply run 'ant update', all your existing, older Solr Schemas &
> Configurations will remain in place unchanged (and new configs/schemas will
> be suffixed with ".new", e.g. schema.xml.new). This could cause instability
> in DSpace if users are accidentally using an old Solr schemas/configurations
> with a new DSpace API.
> I think we need to always overwrite existing Solr Schemas & Configurations.
> If we want to keep around a copy of older Solr Schemas, they should be
> suffixed with "-[date].old" (like when running 'ant -Doverwrite=true
> update'). As users are less likely to customize Solr Schemas/Configs
> (without knowing what they are doing), I think it's better to default to
> overwriting these files during an upgrade.
> As it stands, most users will not even realize there are Solr configurations
> under [dspace]/solr/search/conf/ and [dspace]/solr/statistics/conf/ which may
> not have upgraded properly.
--
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
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
