lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (SOLR-1043) Issue while persisting sharedLib attribute in multicore solr.xml
Date Tue, 17 Mar 2009 15:18:50 GMT

     [ https://issues.apache.org/jira/browse/SOLR-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hoss Man resolved SOLR-1043.
----------------------------

    Resolution: Fixed
      Assignee: Hoss Man  (was: Shalin Shekhar Mangar)

Yeah, i wasn't sure what that line was doing in there either ... i removed it as part of SOLR-1072

> Issue while persisting sharedLib attribute in multicore solr.xml
> ----------------------------------------------------------------
>
>                 Key: SOLR-1043
>                 URL: https://issues.apache.org/jira/browse/SOLR-1043
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 1.3
>            Reporter: karthik c
>            Assignee: Hoss Man
>             Fix For: 1.4
>
>         Attachments: SOLR-1043.patch
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message