-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to SOLR 7 #240
Comments
We needed to do two things when migrating to from Solr 6 to Solr 7.3 on Alpine - we upgraded the JTS spatial lib to jts-core-1.15.0.jar and we also change the solr configs. After this it (so far) seems to run like before. This is what we did in more detail: Upgrade spatial libFor the spatial lib, we had to use a specific version of the JTS lib: /opt/solr/server/solr-webapp/webapp/WEB-INF/lib/jts-core-1.15.0.jar and we had to change any geohash fieldtype solr configs to use spatialContextFactory="JTS" instead of spatialContextFactory="com.spatial4j.core.context.jts.JtsSpatialContextFactory" Config changes in solr.xml and solrconfig.xmlWe had to remove any strings from schema.xml that looks like this:
Instead put those configs in a requestHandler section in solrconfig.xml:
Same for AND operators.... Details here: bioatlas/ala-docker@6599b00#diff-71151dac089a42aaa2630c681b677488 Full details: bioatlas/ala-docker@6599b00#diff-71151dac089a42aaa2630c681b677488 |
Thanks @mskyttner - this is great |
The continued use of Solr-6 has created a security incident for the ALA and possibly other atlases that haven't picked up the Solr-7 patches. This should not have been rated as "Priority-low" and "Enhancement" given the flaw was known and intentionally ignored. |
Can you elaborate on the security incident please @ansell (here or in private comms)?
When those tags were applied it was reasonable to do so (Solr 6 was still actively released) and it is the case that Solr 6 is currently designated as LTS so in theory, but perhaps not in practice one should be ok running on 6 still. It might be worth reporting on the user@ solr list given it is declared LTS. |
thanks @timrobertson100 This is from an old email nearer the time:
I think at this stage we decided to lower the priority because it was deemed to be fixed in 6.6.4. I think the only thing holding us back from using SOLR 7 is the actual task of the upgrading the cluster. I've been testing locally with SOLR 7 for some time with no issues. |
@timrobertson100 The definition of "LTS" that Solr use is different to the way it is used in other projects: http://lucene.472066.n3.nabble.com/Solr-LTS-and-EOL-td4403843.html
Solr-6 has been in stasis since Solr-7 was released, and a bug would need a certain level of impact to be fixed in it, and as soon as 8 is released no bugs will be fixed for it. At that point, Solr-7 will become the version that only gets major bug fixes The Solr-6 bug in this case allowed a solr configuration file to be written, which has been fixed in Solr-7, but has to be explicitly disabled in Solr-6: AtlasOfLivingAustralia/ala-install#231 |
I'm going to close this issue and create an issue in ala-infrastructure repo to upgrade our SOLR cluster to 7. |
If you have recently run the
The ALA will be on Solr-6 until there are resources available to setup a test cluster, but others should be able to use Solr-7 as it has been tested by a few other organisations already. In addition to those, the ALA have a private It is basically the following if you wanted to reuse it:
|
SOLR 7 is out, and should be a relatively easy migration.
The text was updated successfully, but these errors were encountered: