https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937
--- Comment #188 from David Cook <[email protected]> --- (In reply to Ere Maijala from comment #184) > That's because the escaped characters have a special meaning at least in > Elasticsearch, and unless we escape these characters in ES query builder, > they need to be accounted for here. Otherwise ES would balk e.g. trying to > parse [something] as a range. > Ahhhh that's good to know. I thought it was passing the data straight to Zebra, so I was confused why we'd be mangling the data. What you say makes more sense. > I'd be happy to provide some documentation on a wiki page, if that'd be > useful. In the long run this may be used by quite many since it provides > Z39.50 and SRU on top of Elasticsearch, which would otherwise require > running Zebra. Yes please :). I didn't see any references to Elasticsearch in the patches I viewed. I thought it required Zebra to be used. I must've missed the "Add support for SRU and Elasticsearch" patch now that I look again... hehe. It would be great to use this instead of Zebra in that context! I was groaning at the idea of storing MARCXML in MySQL and indexing it into *both* Elasticsearch and Zebra just to get Z39.50 functionality... Nice one, Ere! -- 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/
