IDF boosters in HTTP requests with match about manticoresearch

[sanikolaev]

As discussed, pls prepare a spec on what it should look like in the interface.

[donhardman]

As previously discussed, we expect the structure to be as follows:

"match": {
  "field1,field2": "keyword"
} 

or

"query": {
  "match": {
    "content,title": {
      "query": "keyword",
      "operator": "or"
    }
  }
}

The suggestion is to add a "booster" or something similar at the same level as the "operator". This means that when you use "content,title": "value" and want to include a booster, you should use the following structure:

"content,title": {
  "query": "value",
  "booster": 1.5
}

This approach allows you to boost the relevance of certain fields in your search query, giving them more weight in the results. 😊

[sanikolaev]

Let's call it not booster, but just boost.

[sanikolaev]

@donhardman does this issue block anything?

[donhardman]

Technically, it's not blocking anything. However, we use boost logic to promote the most relevant phrases when forming SQL requests in fuzzy logic. If we don't have it here and use a match with query fields, it will not work for this case.