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.Dear all,
I tried to use latest Solr 5.0.0, but it doesn't work. When I try to create a "core" inside Solr admin, I receive a lot of errors about schema.xml, i.e.
drupal: org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: Could not load conf for core drupal: Unknown fieldType 'file' specified on field eff_*. Schema file is C:\solr\apache-solr\solr\drupal\conf\schema.xml
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | apachesolr-add_solr_5.x_support-2453855-11-7.x.patch | 107.87 KB | jgrubb |
Comments
Comment #1
Nick_vhThis is what I got when trying to run Solr 5.
Start solr
Comment #2
Nick_vhMade the following changes based on https://www.drupal.org/node/2311019
Comment #3
Nick_vhStarted a branch here: http://cgit.drupalcode.org/sandbox-cpliakas-1600962/tree/conf?h=solr5
Comment #4
Nick_vhOutput after that change:
MacBookAir-NickVeenhof:solr-5.0.0 nick.veenhof$ ./bin/solr -f -p 8983
WARNING: Java version 1.7.0_51 has known bugs with Lucene and requires the -XX:-UseSuperWord flag. Please consider upgrading your JVM.
Starting Solr on port 8983 from /Users/nick.veenhof/Servers/solr-5.0.0/server
Comment #5
Nick_vhSomething that jumps out to me:
3875 [coreLoadExecutor-5-thread-1] WARN org.apache.solr.core.SolrResourceLoader – Solr loaded a deprecated plugin/analysis class [solr.admin.AdminHandlers]. Please consult documentation how to replace it accordingly.
4059 [coreLoadExecutor-5-thread-1] WARN org.apache.solr.handler.admin.AdminHandlers – class="solr.admin.AdminHandlers" /> is deprecated . It is not required anymore
Comment #6
drunken monkeySince we are now discussing in #2442077: Support for Solr 5, maybe this one should be closed as a duplicate?
Comment #7
Nick_vhClosing as duplicate
Comment #8
japerryI don't think this is a duplicate. While solr5 configurations have been moved to search api, they haven't been brought over to apachesolr from the common configurations.
Shouldn't this issue be open until the configuration is committed to this project?
Comment #9
geerlingguy CreditAttribution: geerlingguy as a volunteer commented@japerry - Agreed. There was even a blog post on the planet today (Search API and Solr 5) that mentioned how easy it is to start using Solr 5.x with Search API. It would be great to get feature parity again between the two modules, since 5.x has been the stable release for about 6 months now.
Comment #10
protools CreditAttribution: protools commentedany progress ? can i use Apache Solr Search Apache Solr 5.x ?
Comment #11
jgrubb CreditAttribution: jgrubb as a volunteer commentedHere's a patch for this module. I've been using this config in production since July with no problems.
Comment #12
jgrubb CreditAttribution: jgrubb as a volunteer commentedComment #13
geerlingguy CreditAttribution: geerlingguy as a volunteer commentedFor some reason the commit was never logged back to this issue... here it is, for posterity: http://cgit.drupalcode.org/apachesolr/commit/?id=7ba1577
Comment #14
jgrubb CreditAttribution: jgrubb as a volunteer commentedI'm a noob at committing to contrib. Might've messed up the format of the commit msg? Thanks...
Comment #15
geerlingguy CreditAttribution: geerlingguy as a volunteer commented@jgrubb - No problem... as long as it starts with something like
Issue #XYZ, I think it should pop back in here correctly. Just checked the commit message and GitHub-style messages like "Fixes #XYZ" doesn't trigger the comment on drupal.org, unfortunately :(Comment #16
jgrubb CreditAttribution: jgrubb as a volunteer commentedOooo, right. I've been just taking the commit messages they provide below since then and they seem to Just Work. Thank you...
Comment #18
nerdcore CreditAttribution: nerdcore at OpenConcept Consulting Inc. commentedEarlier this week I moved some sites from apachesolr-7.x-1.7 to apachesolr-7.x-1.7+11-dev which contains the solr-5.x conf directory and necessary files for the shiny new Solr 5.x server I've setup.
Then yesterday a security update was released, apachesolr-7.x-1.8: https://www.drupal.org/node/2627580
I was excited to be able to move back to a stable release, but was surprised to discover that apachsolr-7.x-1.8 does NOT contain the
solr-conf/solr-5.xfolder.So, in order to address the ability to delete secondary search environments (the security issue), will I need to resurrect my Solr 4.x server for all my sites using this module? What happened to the solr-5.x configs in the latest stable release?
Comment #19
jgrubb CreditAttribution: jgrubb as a volunteer commentedThat wasn't a stable release, those were just committed on the dev branch. Yesterday's security release was cut off the most stable release just to avoid any possible problems. I'm planning on getting together with @pwolanin tomorrow and hopefully getting these more recent commits into a new stable release.
Comment #20
emerham CreditAttribution: emerham as a volunteer commentedHow did that meeting go?
Comment #21
joseph.olstadRTBC+ for patch #11
We need solr 5.x support added back to the 7.x-1.x dev branch
Comment #22
joseph.olstadI created a related issue for this..
Comment #23
RoSk0Code for this issue is not lost, just checked this.
Comment #24
marcvangendActually, "Closed (fixed)" would be a better status, given that code has been committed for this issue. I'm setting it to "Fixed" so it will auto-close in 2 weeks.
Meanwhile, I posted a minor follow-up in #2879336: Solr 5 config name is incorrect.
Comment #25
joseph.olstadah yes, you are correct @marcangend , I was in the middle of a sprint doing a site with solr when I posted that message, I ended up using the dev release 7.x-1.x , perhaps a tag should be made for 7.x-1.9 with this fix added :
#2879336: Solr 5 config name is incorrect