Hello, This is making my logic a little fuzzy, but I'm wondering if this change would allow an update of the SOLR configs without an update of the dspace/config configs? I don't know that it's a real-life concern, but it seemed worth asking about. (Personally, I'd be just as happy if all configs updated with a plain 'ant update', but I don't make all those changes in the source code, and that may not be typical.)
B-- >>> On 8/8/2011 at 3:21 PM, in message <831492308.5090.1312838477814.JavaMail.jira@atlas>, "Tim Donohue (DuraSpace JIRA)" <[email protected]> wrote: > By default, Solr Schema's & 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.2, 1.7.1, 1.7.0 > 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. ------------------------------------------------------------------------------ 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
