Package Details: elasticsearch 8.17.0-1

Git Clone URL: https://aur.archlinux.org/elasticsearch.git (read-only, click to copy)
Package Base: elasticsearch
Description: Free and Open, Distributed, RESTful Search Engine
Upstream URL: https://www.elastic.co/elasticsearch/
Licenses: custom:Elastic-2.0
Conflicts: elasticsearch-bin, elasticsearch7
Provides: elasticsearch
Submitter: hashworks
Maintainer: ipaqmaster
Last Packager: ipaqmaster
Votes: 11
Popularity: 0.057494
First Submitted: 2022-01-08 16:30 (UTC)
Last Updated: 2024-12-12 16:50 (UTC)

Dependencies (2)

Required by (18)

Sources (9)

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 14 Next › Last »

HLFH commented on 2023-06-20 07:12 (UTC)

Is there a way we can prevent this from falling so far behind the other key Elastic programs?

Flagging out-of-date. And I guess I could try to use automation with Renovate: https://docs.renovatebot.com/user-stories/maintaining-aur-packages-with-renovate/.

If the maintainer of this package and beats are willing, this one could be deleted and added as a subpackage of beats.

Not sure why elasticsearch should be a subpackage of beats.

HLFH commented on 2023-06-20 07:04 (UTC)

elasticsearch has been updated to 8.8.1.

xiota commented on 2023-06-19 23:17 (UTC)

@ipaqmaster If the maintainer of this package and beats are willing, this one could be deleted and added as a subpackage of beats.

Otherwise, flag out of date?

ipaqmaster commented on 2023-06-17 02:15 (UTC)

The Filebeat AUR package is shipping 8.8.1 but this package is shipping 8.7.1. This is a 'huge' problem because Filebeat throws this trying to ship logs to it by default:

Connection marked as failed because the onConnect callback failed: Elasticsearch is too old. Please upgrade the instance. If you would like to connect to older instances set output.elasticsearch.allow_older_versions to true.

Is there a way we can prevent this from falling so far behind the other key Elastic programs? They're supposed to be a suite but I often run into issues with this package falling behind.

HLFH commented on 2023-05-16 09:17 (UTC)

@mklein994 Thanks! I updated the package.

mklein994 commented on 2023-05-15 19:45 (UTC)

I'm getting an error message when I start elasticsearch.service (version 8.7.1-1):

Starting Elasticsearch...
warning: ignoring JAVA_HOME=/usr/lib/jvm/default-runtime; using bundled JDK
/usr/share/elasticsearch/bin/elasticsearch-cli: line 14: /usr/share/elasticsearch/jdk/bin/java: No such file or directory
elasticsearch.service: Control process exited, code=exited, status=127/n/a
elasticsearch.service: Failed with result 'exit-code'.
Failed to start Elasticsearch.

The package is still creating a symlink to JDK 19 (PKGBUILD:59):

ln -s /usr/lib/jvm/java-19-openjdk "$pkgdir"/usr/share/elasticsearch/jdk
#                       ^^-- should this be 20?

The jre-openjdk-headless package is currently at 20.0.1.u9-3. Changing the symlink in the PKGBUILD to java-20-openjdk seems to fix it.

HLFH commented on 2023-05-02 17:52 (UTC)

elasticsearch 8.7.1 released with updated JRE dependency.

synthead commented on 2023-05-02 15:44 (UTC)

Elasticsearch 8.7.1 was released today: https://www.elastic.co/downloads/elasticsearch

D3vil0p3r commented on 2023-04-29 12:21 (UTC)

Hey @HLFH I went in deep on this. Elasticsearch 8.7.x is compatible also with JRE OpenJDK 17 (that is LTS), as discussed today here: https://discuss.elastic.co/t/arch-linux-jre19-openjdk-eol-dependency/331124/3 and shown here: https://www.elastic.co/support/matrix#matrix_jvm

At this point I think that a good solution could be to change that EOL dependency to jre17-openjdk-headless and it will be compatible also with the new 8.7.1 version.

HLFH commented on 2023-04-28 18:01 (UTC) (edited on 2023-04-28 18:02 (UTC) by HLFH)

Well, I am not the guy that deleted JDK19 on the AUR... https://github.com/elastic/elasticsearch/pull/94600
Elasticsearch 8.7.1 does not seem to be yet released, and it is the version that supports JDK20, let me have a look for a workaround.