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

Update to new Metafacture dependency; use Java 11 #130

Merged
merged 7 commits into from
Mar 27, 2025

Conversation

dr0i
Copy link
Member

@dr0i dr0i commented Feb 6, 2025

See #129 & https://jira.hbz-nrw.de/browse/RPB-266.
Don't forget to "export JAVA_HOME=$yourPath".

AFAIK the only problem is the "org.elasticsearch" % "elasticsearch" % "1.7.5" dependency which is used by Classification.java as intrnal lookup for classifications.

Don't forget to "export JAVA_HOME=$yourPath".
@dr0i dr0i changed the title Update to new Metafacture dependency; use Java 11 (#129) Update to new Metafacture dependency; use Java 11 Feb 6, 2025
@dr0i
Copy link
Member Author

dr0i commented Feb 7, 2025

Discussed with @fsteeg :

  1. analyzing what is achieved by the ES index. If it's used only as a lookup we could switch to use a table instead. If elaborate searches are done we could ->
  2. switch to use our ES cluster and refactor to the new API of ES 5.6.3.

@dr0i dr0i self-assigned this Feb 7, 2025
@fsteeg fsteeg linked an issue Mar 7, 2025 that may be closed by this pull request
@acka47
Copy link
Contributor

acka47 commented Mar 10, 2025

@dr0i We will need the newest Metafacture versions soon and, thus, have to switch to Java 11. Can you please prioritize this? (Keep in mind: If this gets too complex, we could also evaluate other approaches that don't require Java11 for RPB.)

@fsteeg
Copy link
Member

fsteeg commented Mar 10, 2025

AFAIK the only problem is the "org.elasticsearch" % "elasticsearch" % "1.7.5" dependency

Am I understanding this correctly? The elasticsearch 1.7.5 dependency is not available for Java 11?

@dr0i
Copy link
Member Author

dr0i commented Mar 10, 2025

AFAIK the only problem is the "org.elasticsearch" % "elasticsearch" % "1.7.5" dependency

Am I understanding this correctly? The elasticsearch 1.7.5 dependency is not available for Java 11?

Yes - I think so.

@dr0i dr0i removed their assignment Mar 10, 2025
@fsteeg
Copy link
Member

fsteeg commented Mar 10, 2025

The build here seems to fail for an unrelated reason:

https://github.com/hbz/rpb/actions/runs/13180450569/job/36789667677#step:5:1937

unresolved dependency: org.metafacture#metafix;1.2.0: not found

@dr0i
Copy link
Member Author

dr0i commented Mar 10, 2025

Ah, ok. Have you tried build it locally with installed mf-fix 1.2.0?

@fsteeg
Copy link
Member

fsteeg commented Mar 10, 2025

No, I have never worked on this issue. Also, it contains no changes about the Java version.

@TobiasNx
Copy link
Contributor

TobiasNx commented Mar 10, 2025

I tried it in another context: https://github.com/hbz/rpb/pull/105/files#diff-5c3fa597431eda03ac3339ae6bf7f05e1a50d6fc7333679ec38e21b337cb6721 The build with 1.2.0 works fine here.

PS: I was so bold to push the adjustments to the build.yml

@TobiasNx
Copy link
Contributor

@dr0i @fsteeg after my adjustments now the build works.

fsteeg added 3 commits March 24, 2025 14:37
- We need Java 11 for using the latest Metafacture release
- Elasticsearch 1.x.x does not support Java 11, Elasticsearch
2.x.x does not support dots in field names, 5.6.16 does both
@fsteeg fsteeg force-pushed the 129-switchToJava11AndUpdateMFDependencies branch from acb39fd to e706032 Compare March 25, 2025 10:22
Get tag in GitHub action, add local file to avoid release build
(which requires signing), use resulting SNAPSHOT in build.sbt
@fsteeg
Copy link
Member

fsteeg commented Mar 25, 2025

Assigning @dr0i for review.

Your original statement about Elasticsearch being the problem was actually true, even though the build here did not show that (you probably tested it locally?), since the problem does not appear on running the tests, but only on sbt run and using the app.

I did some remaining changes for switching to Java 11 and updated the Elasticsearch version for the embedded index to 5.6.16 (Elasticsearch 1.x does not support Java 11, Elasticsearch 2.x does not support dots in field names, 5.x does both).

@fsteeg fsteeg assigned dr0i and unassigned fsteeg Mar 25, 2025
@fsteeg
Copy link
Member

fsteeg commented Mar 25, 2025

Deployed to test:

http://test.rpb.lobid.org
http://test.wein.lobid.org

run: |
git clone https://github.com/metafacture/metafacture-fix.git -b 0.7.1
cd metafacture-fix
touch .temp # don't build release, which requires signing
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice trick :)

@dr0i
Copy link
Member Author

dr0i commented Mar 25, 2025

+1

@dr0i dr0i assigned fsteeg and unassigned dr0i Mar 25, 2025
@dr0i
Copy link
Member Author

dr0i commented Mar 25, 2025

(While you are at it - could you also heave other apps to Java 11, like hbz/nwbib#665 ? If they have similar underlying mechanism ... Would be cool if we would only have one Java version at our servers :) )

@fsteeg
Copy link
Member

fsteeg commented Mar 25, 2025

Would be cool if we would only have one Java version at our servers

Yes, that would be nice, and since it's possible here, it seems like it's a realistic goal. But still a little project, for which we should set aside some time, because it's not just nwbib, but also lobid-gnd and lobid-organisations. We could discuss this in our quarterly planning meeting on Monday.

@fsteeg fsteeg merged commit 8bd207f into main Mar 27, 2025
1 check passed
@fsteeg fsteeg deleted the 129-switchToJava11AndUpdateMFDependencies branch March 27, 2025 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Update to Java 11
4 participants