https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5534
--- Comment #18 from Nick Clemens <n...@bywatersolutions.com> --- (In reply to dguidry from comment #17) > We originally installed Koha around May or June of 2016 and would have been > on the 3.22 version that was released at that time. We used defaults for > everything as far as I remember and it appears that we're using Zebra. Is it > possible to switch to ElasticSearch and is it fairly involved to do so? Are > there any other considerations to take into account before doing so? Is > ElasticSearch production-ready? > > Thanks! Elasticsearch is still in testing phase I would say,there are a few things that need to be cleaned up to be production ready, most of them are small issues, but together they would cause some pain points. Most of them relate to indexing configuration and Koha expectations - if you don't define expected fields sortable - sorting causes a failed search for example Setting it up should be fairly straight forward - Mirko has put together a 'koha-elasticsearch' package which will install needed dependencies for koha, and you will need to install Java and Elasticsearch itself. I will work on some of the issues in the coming weeks and update the status page on the wiki and send something to the list. We do need testers and are working on enabling ES on some sandboxes and will update when that work is ready. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org http://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/