[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 #19 from Victor Grousset/tuxayo <victor at tuxayo.net> ---
(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?

(In reply to Nick Clemens from comment #18)
> I believe you can use es directly to update and remove types and avoid
> reindex:
> 
> curl -X POST http://es:9200/_reindex -H 'Content-Type: application/json' -d
> '{"source":{"index": "koha_kohadev_biblios","type": "data"},"dest":{"index":
> "koha_kohadev_biblio_s"}}'
> 
> that reindexes ES internally to remove the types

So it's much faster than reindexing from Koha's data, that's the gain, right?

>  - 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?

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