-
Notifications
You must be signed in to change notification settings - Fork 1
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
Problem: Archivematica doesn't support Elasticsearch 7.x nor OpenSearch 1.x #1548
Comments
I was wondering about this as well (AM support for more recent Elasticsearch version like 7 or 8). According to https://www.elastic.co/support/eol Our internal security scans with Greenbone flag all ES 6.x instances with the highest CVSS score (10). References |
Adding "Status: refining" to indicate that that Artefactual may need to consider licensing considerations etc. before making a final decision on how to tackle this. |
Hi Sarah, do you have an update on this? As verison 6 is quite out of support now. |
Hey @FingerlessGlov3s , its a great question! The landscape has changed a few times on this front. We're currently working on upgrading ES in our sibling project, AtoM, and will be doing the same for Archivematica when we've had a chance to learn some lessons from that. |
Great to hear it's being worked on, is there any timelines for that piece of work, or is it a slow process? |
We do not have a particular timeline that we can commit to at this moment. |
Please describe the problem you'd like to be solved
The latest versions of Archivematica require Elasticsearch 6.x. Elasticsearch recently released version 8 but there were some licensing changes introduced after 7.10.2. OpenSeach (a community-driven fork of ES already in version 1.3.0) claims to be compatible with that ES version until the next major release.
Describe the solution you'd like to see implemented
I'd like to see a version of Archivematica that works with ES 7.x and OpenSearch 1.x. Both support indexes created in ES 6.x without a full reindex and, without worring about ES 8.x, it shouldn't require major changes in the current implementation.
Describe alternatives you've considered
Additional context
For Artefactual use:
Before you close this issue, you must check off the following:
The text was updated successfully, but these errors were encountered: