[ https://issues.apache.org/jira/browse/SOLR-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexandre Rafalovitch closed SOLR-2430. --------------------------------------- Resolution: Won't Fix defaultCoreName does not exist any more. > Swapping cores with persistent switched on should save swapped core to > defaultCoreName > -------------------------------------------------------------------------------------- > > Key: SOLR-2430 > URL: https://issues.apache.org/jira/browse/SOLR-2430 > Project: Solr > Issue Type: Bug > Components: multicore > Affects Versions: 4.0-ALPHA > Environment: CentOS > Reporter: bidorbuy > Labels: core, multicore > > Running on the latest trunk version and configured multi-cores with > persistent turned on and set a default-core. When swapping cores I would have > expected default behavior to be that the swapped core name would be persisted > as the new defaultCoreName. i.e. if switching from primary to staging, the > defaultCoreName should be written to "staging". > When swapping out cores (i.e. from primary to staging) and then restarting > Jetty, Solr falls back to the current configured default-core (=primary) > instead of the previously swapped one (=staging). If this is intended, can > perhaps the swap command be extended to force rewritting Solr.xml > Current config file: > <?xml version="1.0" encoding="UTF-8" ?> > <solr sharedLib="lib" persistent="true"> > <cores adminPath="/admin/cores" shareSchema="true" > defaultCoreName="primary"> > <core name="primary" instanceDir="conf/primary/" > dataDir="../../data/primary"/> > <core name="staging" instanceDir="conf/staging/" > dataDir="../../data/staging"/> > </cores> > </solr> -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org