https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38101
--- Comment #5 from Tomás Cohen Arazi (tcohen) <[email protected]> --- (In reply to Thomas Klausner from comment #4) > I think that the ES index is defined badly. > > The field you are trying to store the data is most likely defined as "type" > : "keyword". "keyword" should only be used for exact match lookups (think > "category") and thus indeed has an upper limit: > https://www.elastic.co/guide/en/elasticsearch/reference/current/keyword.html > > But storing such a huge amount of text into a "keyword" field makes no sense. > > So the proper fix is to index that data into a field that's defined as > "type":"text". (Only then can you do partial matches on the content!) This looked promising but the result was the same. Maybe I'm doing it wrong but this is what I tried: - Added 'text' as an option to the `search_field.type` ENUM definition (kohastructure.sql:5664) but did it directly on the DB. - Changed the attribute `type` for the `note` index definition in mappings.yaml:3075 - Reloaded the mappings, made sure 'text' was set on the DB Running this: $ ktd --shell k$ perl misc/search_tools/rebuild_elasticsearch.pl --biblios --where "biblionumber=3" -v -v gave the same results without my patch. And worked with it. Have you been able to reproduce it? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ 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/
