| Allow bridges to declare how the engine should behave when the user creates a predicate on an object field. For example a "match" predicate on field "color" could result in a boolean query with three "must" clauses on the "color.r" "color.g" and "color.b" fields. Maybe we could implement something similar to HSEARCH-3320 Open , i.e. have the bridge register a callback that would turn a user-defined projection definition into a composite projection (see HSEARCH-3222 Open , and in particular the draft of composite projection APIs here. |