[Koha-bugs] [Bug 33353] Add compatibility with Elasticsearch 8

[bugzilla-daemon at bugs.koha-community.org]

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

--- Comment #20 from Nick Clemens <nick at bywatersolutions.com> ---
(In reply to Victor Grousset/tuxayo from comment #19)
> (In reply to Nick Clemens from comment #17)
> > Making the upgrade of Koha force the ES upgrade without allowing it before
> > feels like it could cause issues
> 
> Thanks for catching that 😱 that's a big miss in my review. Requiring
> reindex wouldn't make the upgrade as simple as hoped.
> 
> How can one reproduce an ES upgrade with KTD? That would mean shutting down
> the ES7 container and restart an ES8 one without loosing the existing data.
> https://www.elastic.co/guide/en/cloud/current/ec-migrating-data.html
> Maybe something with a snapshot and moving the snapshot files out of the
> container and putting then in the ES8 container?
> Or starting a parallel ES8 container, having it replicate the data from the
> ES7 one and replace the ES7 with an ES8 (to have the right container name to
> plug in KTD) and replicate again?

That would be tricky - maybe if you setup a volume, and then just connected new
container to the volume? Or get into the container and perform an upgrade
directly?
I think it should work for testing to spin up on ES7 - apply these patches, ES
won't work, then do the reindex (as below or via Koha) and confirm that it
works. We aren't removing 7 support afaik, but require 7 or higher after this I
believe

> 
> (In reply to Nick Clemens from comment #18)
> > I believe you can use es directly to update and remove types and avoid
> > reindex:
> So it's much faster than reindexing from Koha's data, that's the gain, right?

Yes, as I understand it moves the data to remove the type level, so we don't
have to cycle through every record and parse into ES - I tested at Hackfest and
it was exponentially faster

> 
> >  - it does require renaming
> > the index so would need some sort of alias or something
> 
> Does doing the rename again would allow to get back to original name and
> have no config to touch?

I think you either setup an alias with the old that points to the new name - or
do the reindex, delete the old one, then rename the new one

-- 
You are receiving this mail because:
You are watching all bug changes.