https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38101
Thomas Klausner <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from Thomas Klausner <[email protected]> --- 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!) If this is not possible, you can tell ES itself to cut off the text using `ignore_above`: https://www.elastic.co/guide/en/elasticsearch/reference/current/ignore-above.html So instead of handling this via code as suggested in the patch it should be handled via fixing the ElasticSearch mappings for this (and maybe other) fields. I've taken a quick look at `elasticsearch/mappings.yaml` but did not find any indicator there that 500 should be used as a keyword. BUT: I do not really understand how your solution can fix the issue, so maybe all I'm saying now is wrong... I can try your bug later (not sure if during the weekend) to get a better understanding Greetings domm -- You are receiving this mail because: You are the assignee for the bug. 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/
