Send Koha-devel mailing list submissions to
koha-devel@lists.koha-community.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
or, via email, send a message with subject or body 'help' to
koha-devel-request@lists.koha-community.org
You can reach the person managing the list at
koha-devel-owner@lists.koha-community.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha-devel digest..."
Today's Topics:
1. Re: [Koha] Switching Koha to ElasticSearch... any problems?
(Philippe Blouin)
2. Re: Switching Koha to ElasticSearch... any problems?
(Thomas Klausner)
3. Koha releases are available đ (Mason James)
----------------------------------------------------------------------
Message: 1
Date: Thu, 31 Mar 2022 08:47:03 -0400
From: Philippe Blouin <philippe.blouin@inlibro.com>
To: Mason James <mtj@kohaaloha.com>, "koha@lists.katipo.co.nz"
<koha@lists.katipo.co.nz>, Koha Devel
<koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] [Koha] Switching Koha to ElasticSearch...
any problems?
Message-ID: <fc7128a6-2251-f97b-0d4a-10901337a06f@inlibro.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Hi Mason,
We've made the switch to most of our production systems. The process
was rather simple and the results are much better than before.
Major problem? no. Missing: for one, date range searches do not work
at all. If it matters to your users, thread carefully.
On 2022-03-30 22:52, Mason James wrote:
> hi Folks
> does anyone have any experience running Koha with ES?
>
> i've done some basic testing (on 20.11) - it seems to work well and
> its speed is impressive! (đĻ + đ)
>
> - is it generally safe to run in production?
> - any major problems, or missing areas of functionality?
>
>
> any advice or info would be welcomed
>
> cheers, Mason
> _______________________________________________
>
> Koha mailing list http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
--
Philippe Blouin,
Directeur de la technologie
TÊl. : (833) 465-4276, poste 230
philippe.blouin@inLibro.com
inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220331/be0883ee/attachment-0001.htm>
------------------------------
Message: 2
Date: Thu, 31 Mar 2022 15:15:57 +0200
From: Thomas Klausner <domm@plix.at>
To: "koha@lists.katipo.co.nz" <koha@lists.katipo.co.nz>, Koha Devel
<koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Switching Koha to ElasticSearch... any
problems?
Message-ID: <20220331131557.GR751042@plix.at>
Content-Type: text/plain; charset=utf-8
Hi!
On Thu, Mar 31, 2022 at 03:52:45PM +1300, Mason James wrote:
> does anyone have any experience running Koha with ES?
>
> i've done some basic testing (on 20.11) - it seems to work well and its speed is impressive! (đĻ + đ)
>
> - is it generally safe to run in production?
> - any major problems, or missing areas of functionality?
We launched a big library using ElasticSearch this January, it work very
well, but:
* you need to make sure to give ES the proper resources on the server.
It will need more RAM than Zebra...
* I discovered (and fixed) a few bugs in the ElasticSearch Mappings
Tool, until they are merged (and published in a new release) be very
careful with this DataTable! (30142, 29893, 29010)
* Not all searches use those mappings, eg auth_finder.pl uses hardcoded
MARC fields
* ElasticSearch interprets lowercase boolean ops as literal search
terms. So "foo or bar" finds docs that contain "foo" and "or" and
"bar", but "foo OR bar" finds docs containing either "foo" or "bar".
AFAIK in 20.11 most of these problems are fixed, but see 30153 for a
rather recent fix (which I think is already available in the most
recent point releases)
* One thing that proved problematic during our initial migration of 500k
records was that ElasticSearch indexing is automatically triggered
after each edit for each item. This is fine when editing / catalouging
by hand, because all changes are immediatly available. But during
migration it caused a huge performance hit. There is / was some work
to offload the indexing to a worker process, but I think that's not
done / stalled. So we hacked our instance to skip the immediate
indexing via an ENV var (much easier than passing a command line flag
from the script through several layers of modules)
having said that, I think going with ES is a very smart move, because
(other then Zebra) it's a standard tool with very good docs and a lot of
knowledgable people (i.e. stackoverflow) to help you :-)
Greetings,
domm
--
#!/usr/bin/perl https://domm.plix.at
for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}
------------------------------
Message: 3
Date: Fri, 1 Apr 2022 15:07:48 +1300
From: Mason James <mtj@kohaaloha.com>
To: "koha@lists.katipo.co.nz" <koha@lists.katipo.co.nz>, Koha Devel
<koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Koha releases are available đ
Message-ID: <25b5b960-b3a0-34b4-d0ee-597f1f4bc7c0@kohaaloha.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
kia ora community,
the latest Koha packages are available
installation guide is below...
https://wiki.koha-community.org/wiki/Koha_on_Debian
cheers, Mason
------------------------------
Subject: Digest Footer
_______________________________________________
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/
------------------------------
End of Koha-devel Digest, Vol 197, Issue 1
******************************************