How to use approximate match filter search

Engines Overview Engine
,
1

Peace out,

we heard from Tomas the existing of the “approximate match filter search” which can be used for doing partially search.

When using the overview engine and performing a search with filtering the property foo/bar following filter will be set

“filter”:{“filters”:[“foo.bar:101”]}

Unfortunately this will not trigger the “approx. match filter search” because you have to put a tilde at the beginning, means the filter should look like this:

“filter”:{“filters”:[“~foo.bar:101”]}

Then we would find documents with foo.bar === 101/123/456789 or other values which are containing the given string 101

Do we forgot to set a config or something else in our overview or is this really something which is not implemented currently ?

Best,
Tjorben

2

That is really good to know, @tjorben-atomic-moss. Thank you for sharing it with us!

3

Oh i see that i’ve not really put a question into it :smiley: Of course my question is, if this is possible somehow and we only forgot to set a config or something else.

Will edit my post

4

Hi @tjorben-atomic-moss,

Have you enabled “approximate match filter search” on the document model for the field “bar” yet?

Without the annotation, Data Services will not aware of the field to index beforehand. For the overview engine/client, it will automatically add the “~” into the filter condition whenever it sees a field with that annotation. Therefore, enabling it in the document model is an important part here.

You can have a look at Data Services documentation here:
https://docs.geta12.com/docs/?release=2023.02#content:asciidoc,product:data_services,artifact:dataservices-documentation-src,scene:UaEfdp,release:2023.02,anchor:approximate-match-filter-search

Cheers,
Tri

5

Hey @tri-sheer-boulder

yeah i set the annotation according to your linked page. I even tried it out by sending the correct request to ds and it worked, so i’m sure on DS side everything works find. Only the overview was not able to put a tilde as prefix.

But nice to hear that it should work, so i will further investigate where the problem really lies.

Best,
Tjorben