Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hello,
I use solr 5.5.1 and on Logging page I see warnings, related with deprecated configs:
WARN null Config Solr no longer supports forceful unlocking via the 'unlockOnStartup' option. This is no longer neccessary for the default lockType except in situations where it would be dangerous and should not be done. For other lockTypes and/or directoryFactory options it may also be dangerous and users must resolve problematic locks manually.
WARN null Config Beginning with Solr 5.5, <mergePolicy> is deprecated, use <mergePolicyFactory> instead.
WARN null Config Beginning with Solr 5.5, <mergeFactor> is deprecated, configure it on the relevant <mergePolicyFactory> instead.
I tested this config on solr 5.5.0 and I see these warning too.
Comment | File | Size | Author |
---|---|---|---|
#2 | warnings-in-solrconfig-xml-for-5-x-version-2720349-2.patch | 2.6 KB | zestagio |
solr warnings.png | 33.43 KB | zestagio |
Comments
Comment #2
zestagio CreditAttribution: zestagio commentedComment #3
zestagio CreditAttribution: zestagio commentedComment #4
drunken monkeyThe problem here is that Solr 5.5 introduced some changes that break backwards-compatibility, so we can't really have a set of configuration files that works for all 5.x versions (I think). Or does the
<int name=mergeFactor>
thing also work in earlier versions of Solr 5?If not, then I'd just say we add to the README that we don't support Solr 5.5+ and try to add support for Solr 6 soon. We had the same for Solr 3, we didn't support 3.6 there, either.
Comment #5
zestagio CreditAttribution: zestagio commentedLooks, as the
<int name=mergeFactor>
not work in earlier versions of Solr 5.In this case, I think, that it's solution
Comment #6
drunken monkeyAdded it to the handbook page.
@ Apachesolr guys: Do you want to add such a warning, too, or should we mark this as "fixed"?