https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27091
Bug ID: 27091
Summary: Document how Elasticsearch is supposed to work and
implement respective configurations
Change sponsored?: ---
Product: Koha
Version: master
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5 - low
Component: Searching - Elasticsearch
Assignee: koha-bugs@lists.koha-community.org
Reporter: joonas.kylm...@helsinki.fi
CC: n...@bywatersolutions.com
Elasticsearch is very flexible search engine and has many configuration
options. We should document our expectations on how it should work and also
because then it would allow the users to understand how to form their queries
in the best possible way. After documenting the configuration we want based on
the expectations we should tune the indexing and search configuration
parameters accordingly.
The bug 27070 makes the Elasticsearch searches more Zebra like by trying to
match search keywords across all fields but is this exactly what we want in the
end? What if we have only a number in the search query should we try to query
numeric fields then only or also string fields? How should the weights work?
For weight documentation we should have an basic configuration for it in our
default mappings.yaml file so that we have some idea how it will be used in
real world.
--
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
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/
