[
https://jira.duraspace.org/browse/DS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21655#comment-21655
]
Tim Donohue commented on DS-987:
--------------------------------
We discussed this issue in Today's Developers Meeting.
Richard Rodgers actually pointed out there are two intermingled issues here.
(1) Whether or not we should default "overwrite=true" for the Configurations in
[dspace]/config/. Most in the discussion liked this idea, but that we should
make this abundantly clear to everyone that the default value has changed!
I'll create a new JIRA issue for this shortly.
(2) Whether or not "overwrite" flag should have any control over the Solr
Internal Configs at [dspace]/solr/*/conf/. We ran out of time during this part
of the discussion.
In my opinion, the Solr Schema needs to *always* be updated during an upgrade
(no matter what "overwrite" is set to). If you don't upgrade the Solr Schema,
then DSpace cannot ensure it will be able to communicate properly with Solr
(and you may end up with unexplained odd behavior, etc.). Just like we don't
give an option as to whether or not you upgrade your DB Schema, we shouldn't
give an option as to whether or not your upgrade your Solr Schema.
> 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
------------------------------------------------------------------------------
uberSVN's rich system and user administration capabilities and model
configuration take the hassle out of deploying and managing Subversion and
the tools developers use with it. Learn more about uberSVN and get a free
download at: http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
