[
https://jira.duraspace.org/browse/DS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21658#comment-21658
]
Mark Diggory commented on DS-987:
---------------------------------
(1) glad we agreed on this.
(2) the problem is that we customize the local solr schemas, so forcing
overwriting them in all cases prevents allowing this. I think its best to keep
the logic consistent so that all of dspace-dir is treated similarly. (a)
overwrite with backup by default (b) overwrite=false as optional
parameterization.
> 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
> 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
------------------------------------------------------------------------------
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
