The behavior should be to combine the two set to the level of field name. This is so some default filter/boost can be set and added to in the query. Currently fields in the query completely replace those in engine.json.
Use case: in engine.json specify an "availability": "true", then in the query supply the category boosts.
The behavior should be to combine the two set to the level of field name. This is so some default filter/boost can be set and added to in the query. Currently fields in the query completely replace those in engine.json.
Use case: in engine.json specify an "availability": "true", then in the query supply the category boosts.