Summary: | Document how Elasticsearch is supposed to work and implement respective configurations | ||
---|---|---|---|
Product: | Koha | Reporter: | Joonas Kylmälä <joonas.kylmala> |
Component: | Searching - Elasticsearch | Assignee: | Bugs List <koha-bugs> |
Status: | Needs documenting --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | andrew, emmi.takkinen, f.demians, jonathan.druart, mtj, nick |
Version: | Main | Keywords: | Manual |
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27070 | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Joonas Kylmälä
2020-11-25 13:22:46 UTC
Some links that contain information that might be useful for the decision making: https://discuss.elastic.co/t/cross-fields-and-boost-is-it-feasible/134219/11 https://wiki.koha-community.org/wiki/Elasticsearch https://www.elastic.co/guide/en/elasticsearch/reference/master/query-dsl-multi-match-query.html https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-boost.html Where could this documentation take place? Koha wiki? What should it cover exactly? We should stop now adding functionalities, or fine tuning an implementation which is obfuscated by overengineering. (In reply to Frédéric Demians from comment #2) > Where could this documentation take place? Koha wiki? What should it cover > exactly? We should stop now adding functionalities, or fine tuning an > implementation which is obfuscated by overengineering. As a lot of libraries are already using Elasticsearch in production stopping the fine tuning and bug fixing appears not possible. What would you suggest? |