As analyzed by work that was done at Acquia we figured out that relying on the default MergePolicy was not ok. More about this can be read here :
http://www.nickveenhof.be/blog/upgrading-apache-solr-14-35-and-its-impli...

CommentFileSizeAuthor
#2 1427288-2.patch2.79 KBnick_vh
#1 1427288-1.patch942 bytesnick_vh

Comments

nick_vh’s picture

StatusFileSize
new942 bytes
nick_vh’s picture

StatusFileSize
new2.79 KB

Changes in schema or solrconfig should be visible in the name

nick_vh’s picture

Version: 7.x-1.x-dev » 6.x-3.x-dev
Status: Active » Patch (to be ported)

Committed

pwolanin’s picture

Version: 6.x-3.x-dev » 7.x-1.x-dev
Status: Patch (to be ported) » Needs work

should be "rc1" as the version where it will be released?

nick_vh’s picture

Well, since we do not know that yet I didn't want to run ahead of time :-)
When we go RC1 we can change the versions?

nick_vh’s picture

Title: Change the MergePolicy for all the solrconfigs to use LogByteMergePolicy » Update all solr configs to have version number RC1
nick_vh’s picture

Status: Needs work » Closed (fixed)

Closing this one - Sounds logical that we need to do this