Skip to content
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

Open
5 tasks
jraddaoui opened this issue Mar 31, 2022 · 6 comments
Open
5 tasks
Labels
Status: refining The issue needs additional details to ensure that requirements are clear.

Comments

@jraddaoui
Copy link

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:

  • All pull requests related to this issue are properly linked
  • All pull requests related to this issue have been merged
  • A testing plan for this issue has been implemented and passed (testing plan information should be included in the issue body or comments)
  • Documentation regarding this issue has been written and merged
  • Details about this issue have been added to the release notes
@jens-st
Copy link

jens-st commented Aug 11, 2022

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
the latest ES 6.x Version (6.8.23) is EOL since 2022-02-10 (the release of ES 8.0) and is no longer maintained.

Our internal security scans with Greenbone flag all ES 6.x instances with the highest CVSS score (10).

References
Manual Install Ubuntu: https://www.archivematica.org/en/docs/archivematica-1.13/admin-manual/installation-setup/installation/install-ubuntu/#ubuntu-18-04-bionic-installation-instructions
Ansible Playbook Ubuntu: https://github.com/artefactual/deploy-pub/blob/master/playbooks/archivematica-bionic/vars-singlenode-1.13.yml#L28

@sromkey sromkey added triage-release-1.14 Status: refining The issue needs additional details to ensure that requirements are clear. labels Aug 15, 2022
@sromkey
Copy link
Contributor

sromkey commented Aug 15, 2022

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.

@FingerlessGlov3s
Copy link

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.

@sromkey
Copy link
Contributor

sromkey commented Oct 18, 2024

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.

@FingerlessGlov3s
Copy link

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?

@sromkey
Copy link
Contributor

sromkey commented Oct 18, 2024

We do not have a particular timeline that we can commit to at this moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: refining The issue needs additional details to ensure that requirements are clear.
Projects
None yet
Development

No branches or pull requests

5 participants