https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25669
--- Comment #26 from Victor Grousset/tuxayo <[email protected]> --- Thanks Kevin for the clarifications. > It will work as long as support before 6.7 is not required I would say that's not a problem. ES <= 6.7 (even 6.8 actually) has security issues and is upgradable to 6.8.x directly. (In reply to Julian Maurice from comment #25) > Still unsure about how to do that. We have a few possible solutions: > 1) Have a switch in $KOHA_CONF or in a syspref that enable/disable types > 2) Have the version of ES in $KOHA_CONF or in a syspref (it might be better > to have the version than several "feature switches") If we need a syspref or config switch, we can count on part of instances not knowing that it's needed. > 3) Detect the version of ES at indexing time. > > solution 3 might cause performance issues when indexing directly (for > instance after a biblio modification). They can be mitigated by either: > a) put the version in memcached or L1 cache, but now there's a cache issue > (you'd have to remember to flush the cache when upgrading ES) What if we refresh the ES version cache value on each services start? Surely there isn't the need to upgrade ES on the fly without even restarting the services. (wait, for installs without plack, do we have the concept of "restarting the services"?) Or maybe on ES connection init? (I don't know if it's kept alive or opened on each request) > b) use bug 27344 to index in a background job It would make it not backportable. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://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/
