Yes, this did change - it's actually a protection for a previous change though.
There was a time when you did a core reload by just making a new core with the same name and closing the old core - that is no longer really supported though - the proper way to do this is to use SolrCore#reload, and that has been the case for all of 4.x release if I remember right. I supported making this change to force people who might still be doing what is likely quite a buggy operation to switch to the correct code. Sorry about the inconvenience. - Mark On May 23, 2013, at 10:45 AM, André Widhani <andre.widh...@digicol.de> wrote: > It seems to me that the behavior of the Core admin action "CREATE" has > changed when going from Solr 4.1 to 4.3. > > With 4.1, I could re-configure an existing core (changing path/name to > solrconfig.xml for example). In 4.3, I get an error message: > > SEVERE: org.apache.solr.common.SolrException: Error CREATEing SolrCore > 'core-tex69b6iom1djrbzmlmg83-index2': Core with name > 'core-tex69b6iom1djrbzmlmg83-index2' already exists. > > Is this change intended? > > André >
