https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38345

--- Comment #23 from Victor Grousset/tuxayo <[email protected]> ---
Even if forking Search::Elasticsearch wasn't really yet on the table for
OpenSearch support, it might be needed sooner than we think for all future
Elasticsearch support.
See Bug 39174: Search::Elasticsearch is being retired. And if ES 9 (coming
likely in summer or September) doesn't work out of the box then that will be
it. No support.
And if we don't find a way to make ES 9 work before 26.11 LTS release, it will
end up stuck with only supporting ES 8 which will very likely be EOL before
2030-05

-------

There is an OpenSearch perl client: https://metacpan.org/dist/OpenSearch
Looking at the multiple release changelogs, I guess it should do the job for
base features, but it certainly doesn't support Elasticsearch (it's not a fork
of Search::Elasticsearch)
But there still might be a path there in helping to add ES support. Since there
is no ES perl client anymore, if we are lucky, it might be welcomed there to
have contributions from people using ES with Perl. And we are not the only ones
interested in the future of ES Perl support:
https://github.com/elastic/elasticsearch-perl/issues/220

So that's another option. In addition with forking Search::Elasticsearch and
trying to add future OpenSearch 3.X support. And maybe proposing to the people
making the OpenSearch perl lib to join forces here.

Devs at ES seem open to giving some pointers to help supporting future ES
versions with perl:
https://github.com/elastic/elasticsearch-perl/issues/220#issuecomment-1196582337
Which would still help even if going the path of adding ES support to the
OpenSearch perl lib.

Also at Opensearch there might be some support:
https://opensearch.org/blog/community-clients/
It lists elasticsearch-perl as needing a fork. Which would get help.

Any of those paths might benefit from a name not tied to one of the products to
make more clear to the users that the support is dual. And to have more chances
getting some help when need from the two products. Since the user base is
small, it might be tough enough already.
(Just seeding the idea for later.)

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to