I'd say that you're right in that Solr is the only viable alternative.
Which, from my point of view, is actually quite thrilling since I feel
much more at home with Solr. That said, I find it just a little bit
annoying how often it seems that something that happens outside your
core of work forces you to do a lot of extra work.
I've yet to encounter an ILS with enough records to need clustering. Our
discovery interface uses Solr with a 6-shard SolrCloud instance, but
then it's 80+ million records. So I believe this won't be an issue. Solr
also support sharding without SolrCloud, but it's still somewhat complex
and not automatic like with ES. Though I read somewhere that ES is also
moving to default to a single shard.
While both are Lucene-based, they're quite different. Or rather, the
approaches they take are quite different. ES to me feels more like "make
it easy to get started, but beware, there will be obstacles", while Solr
is more like "here's what you need to consider before getting started,
and it may feel daunting, but you'll be much more informed in the long run".
Luckily, I think that with Koha the largest amount of work with ES has
been in getting to the point where it's not assuming Zebra everywhere.
This would make the task of introducing Solr much more reasonable.
--Ere
dc...@prosentient.com.au kirjoitti 18.1.2021 klo 3.08:
I wonder that too. In the past, Solr didn't have cluster options, but it seems
like it might have SolrCloud now for that? I think it uses Apache ZooKeeper
which adds overhead and complexity. Elasticsearch's clustering is a lot more
self-contained if I recall correctly. But then clustering would only be needed
for more advanced implementations...
But Solr is probably the only viable alternative to Elasticsearch at this point?
David Cook
Software Engineer
Prosentient Systems
Suite 7.03
6a Glen St
Milsons Point NSW 2061
Australia
Office: 02 9212 0899
Online: 02 8005 0595
-----Original Message-----
From: Koha-devel <koha-devel-boun...@lists.koha-community.org> On Behalf Of
Joonas Kylmälä
Sent: Friday, 15 January 2021 9:07 PM
To: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] Elasticsearch changing licences
Ḧi,
yeah, just heard about this. We might want to start looking into some community
developed solution, maybe solr?
Joonas
On 15/01/2021 07:22, dc...@prosentient.com.au wrote:
Hi all,
Have folk heard that Elastic is changing the Elasticsearch licence?
Depending on your sources and your beliefs, this may or may not
matter, but certainly something to be aware of.
https://www.elastic.co/pricing/faq/licensing
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/ git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/
--
Ere Maijala
Kansalliskirjasto / The National Library of Finland
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/
