Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.3
-
None
-
None
Description
I executed a core admin command to dynamically create a new core in Solr with the persist flag set to true as mentioned here: http://wiki.apache.org/solr/CoreAdmin#head-7ca1b98a9df8b8ca0dcfbfc49940ed5ac98c4a08.
The core properties like name and instanceDir were persisted properly in the solr.xml. However, the relative path specified in the sharedLib attribute of the top level "solr" element got converted by its absolute path. This caused errors in loading the classes in the sharedLib when the server is subsequently restarted. Manually changing the sharedLib back to its relative path fixes this issue.
Attachments
Attachments
Issue Links
- is part of
-
SOLR-1072 absolute path for sharedLib is treated as a relative path
- Closed