lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <>
Subject Re: Reverse-engineering existing installation
Date Sat, 04 May 2019 03:53:43 GMT
Wait. I was recommending you diff the 4.2.1 solrconfig and the solrconfig you’re using. Ditto
with the schema. If you’re trying to diff the 7x or 8x ones they’ll be totally different.

But if you are getting massive differences in the yo4.2.1 stock and what you’re using, then
whoever set it up made the changes and you’ll probably have to go through them by hand,
noting all the differences in the non-commented parts.

Things that are _missing_ from the one you’re using .vs. the stock distro files you can
pretty much ignore. They’ll be interesting in that you can delete the equivalent from the
new distro, but…

I expect the schema will be the most different, solrconfig usually doesn’t change much.


> On May 3, 2019, at 7:30 PM, Doug Reeder <> wrote:
> Thanks! Diffs for solr.xml and zoo.cfg were easy, but it looks like we'll
> need to strip the comments before we can get a useful diff of
> solrconfig.xml or schema.xml.  Can you recommend tools to normalize XML
> files?  XMLStarlet is hosted on SourceForge, which I no longer trust, and
> hasn't been updated in years.
> On Fri, May 3, 2019 at 4:24 PM Shawn Heisey <> wrote:
>> On 5/3/2019 1:44 PM, Erick Erickson wrote:
>>> Then git will let you check out any previous branch. 4.2 is from before
>> we switched to Git, co I’m not sure you can go that far back, but 4x is
>> probably close enough for comparing configs.
>> Git has all of Lucene's history, and most of Solr's history, back to
>> when Lucene and Solr were merged before the 3.1.0 release.  So the 4.x
>> releases are there:
>> --------------------
>> elyograg@smeagol:~/asf/lucene-solr$ git checkout
>> releases/lucene-solr/4.2.1
>> Checking out files: 100% (13209/13209), done.
>> Note: checking out 'releases/lucene-solr/4.2.1'.
>> You are in 'detached HEAD' state. You can look around, make experimental
>> changes and commit them, and you can discard any commits you make in
>> this state without impacting any branches by performing another checkout.
>> If you want to create a new branch to retain commits you create, you may
>> do so (now or later) by using -b with the checkout command again. Example:
>>   git checkout -b <new-branch-name>
>> HEAD is now at 50c41a3e5c Lucene Java 4.2.1 release.
>> --------------------
>> Thanks,
>> Shawn

View raw message