I’m trying to normalize the score to apply a threshold using $match to improve the search abilities, but the steps $addField, $setWindowFields and $addField are taking too long, How can I improve this step?
Skip to main content
First - help us understand why you need to normalize scores (generally that’s not done) - can you explain the scenario?
Also, can you provide the query aggregation pipeline? Note that stages that appear after $search will consume the full set of search results at that point - so do a $limit before those stages if possible, otherwise things will slow down the more results you have.
New & Unread Topics
| Topic | Replies | Views | Activity |
|---|---|---|---|
| Dedicated search nodes on Azure now in private preview | 0 | 673 | May 2024 |
| Not getting ‘highlights’ and ‘score’ values in Atlas function | 2 | 516 | Jun 2024 |
| Updating indexes as part of deploy server build process? | 0 | 175 | Jul 2024 |
| How to set up atlas search index with autocomplete for field inside an array? | 1 | 54 | Nov 2024 |
| MongoDBAtlasVectorSearch seems to return “empty response” | 0 | 42 | Nov 2024 |