https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12872 --- Comment #31 from Nick Clemens <nick@bywatersolutions.com> --- (In reply to Marcel de Rooy from comment #30)
(In reply to Katrin Fischer from comment #29)
Hi Marcel and Kyle, what's needed to get this moving again? Would love to be able to exclude the internal notes from being indexed (bug 15050) Hard to say.
Another question is: If we exclude field A from Zebra, do we need to exclude it from ElasticSearch too ? If we add a pref or a config var, it is on the instance level. We probably don't want it to be on search engine level ?
Nick: Could you please report the current status of Elastic in this regard? How can I exclude a specific field from indexing per INSTANCE in Elastic now ?
I would say yes, if excluding from Zebra we should exclude from Elastic, I am having a hard time thinking of a reason you would only want to exclude form one search engine. Currently ES implementation doesn't support this, we push the entire record into the '_all' field. Catmandu fixes do allow exclusion of fields I believe, so we should be able to add the ability to exclude fields into the configuration section, or in a syspref, to allow this per instance -- You are receiving this mail because: You are watching all bug changes.