https://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362013-10-09T23:02:43ZEcoinformatics RedmineMetacat - Story #6114: Include updated D1 indexing libraryhttps://projects.ecoinformatics.org/ecoinfo/issues/6114?journal_id=208972013-10-09T23:02:43ZJing Taotao@nceas.ucsb.edu
<ul></ul><p>After changing the version depency on the metacat-index pom.xml and some code change, the new version works.</p>
<p>There is an issue here:</p>
<p>how can we copy the new schema.xml to overwrite the existing /solr-home/conf/schema.xml?</p>
<p>Here is my thought:</p>
<p>1. During the configuration (installation), the hash of the existing schema.xml will be calculated. <br />2. If the hash value indicates that the schema.xml wasn't changed, the installation process will overwrite the existing one silently. I guess the possibility of the case will be more than 90%.<br />3. If the schema.xml was changed, we should show a message to ask the user manually merge the difference and put the new one into the place.</p> Metacat - Story #6114: Include updated D1 indexing libraryhttps://projects.ecoinformatics.org/ecoinfo/issues/6114?journal_id=209112013-10-10T19:11:53Zben leinfelderleinfelder@nceas.ucsb.edu
<ul><li><strong>Target version</strong> changed from <i>2.2.1</i> to <i>2.3.0</i></li></ul> Metacat - Story #6114: Include updated D1 indexing libraryhttps://projects.ecoinformatics.org/ecoinfo/issues/6114?journal_id=210072013-10-30T15:49:58Zben leinfelderleinfelder@nceas.ucsb.edu
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul><p>I believe this is complete.</p>