[regression:0.99.3-0.99.4] Advanced search may return more results than desired (possibly contributed by fuzzy search)

[rom1dep]

Description

(@eliandoran , @perfectra1n as discussed on Matrix and reproed by juju123)

0.99.3 (good)

0.99.4 (bad)

This last screenshot shows the search algorithm coming-up with "Walk the dog" as a result, despite the ~status value being "Not Started" (while the user wants an exact match for "Started").

TriliumNext Version

0.99.4

What operating system are you using?

Other Linux

What is your setup?

Local (no sync)

Operating System Version

Linux

Error logs

No response

[dosubot]

This regression is likely caused by changes to the fuzzy search logic in recent versions. In 0.99.4, advanced search filters like status.title="Started" may match non-exact values (such as "Not Started") because fuzzy matching is applied to metadata fields, not just full text. The intended behavior is for the = operator to disable fuzzy search and force exact matches, but maintainers have confirmed that this currently only works for full text search, not for metadata or titles, which explains the broader results you're seeing (source). There is ongoing discussion about adding an option or operator to force exact matches for metadata fields, but no fix is available yet.

For now, there is no configuration or workaround in 0.99.4 to force exact matching for metadata fields in advanced search. If you need strict filtering, you may need to manually review results or consider downgrading until a fix or option is released. Keep an eye on related issues and discussions for updates (source).

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[contributor]

Yes, it returns too much/wrong results. Not only for advanced search. Just for simple word search. It has been broken for couple of versions now. Fuzzy search is not good and slow for my use cases. Option to disable it is welcome.

There are in-flight issues and PRs regarding that.

Search function slow since 0.98.0 · Issue #6808 · TriliumNext/Trilium

Fuzzy search should have a "non fuzzy" option · Issue #6765 · TriliumNext/Trilium

[perfectra1n]

I knew you would appear out of the woodwork since the issue mentioned fuzzy search 😂
(specifying ="pagio" should now work as expected, but that's another tangent separate from this)

[contributor]

specifying ="pagio" should now work as expected,

well, it still does not work in 0.99.5

[perfectra1n]

WELL then, we need to talk to this perfectra1n guy's manager!

[contributor]

WELL then, we need to talk to this perfectra1n guy's manager!

Not sure what that means. But =pagio in 0.99.5 finds only one note that contains the search term. But there are dozens such notes in db. This can be called "work as expected".

[contributor]

But =pagio in 0.99.5 finds only one note that contains the search term. But there are dozens such notes in db. This can be called "work as expected".

This was reported previously here, and it is still the case:
#7268 (comment)