Hi all, we're building a prototype for a big custo...
# community-help
k
Hi all, we're building a prototype for a big customer who probably wants to use TypeSense as their new search engine instead of Elastic search. We are currently running into one issue. The Dutch ('nl') stemmer doesn't seem to work properly when searching. When I'm searching on 'handschoenen' (= gloves plural in Dutch), the engine is not returning 'handschoen' (glove singular in Dutch). The other way around everything is working fine. I've setup the field like this: { "name": "product_description", "type": "string", "optional": true, "locale": "nl", "stem": true } Am I doing something wrong? Hope you can help me and we can advice this customer to use Typesense.
j
We had a few some stemming bugs in v27.1. Could you try with v28.0.rc36 and if you can still replicate it, could you share a minimal set of curl commands like this and put it in a GitHub issue so we can look into it?
k
Hi Jason, I tried with v28.0.rc35. Was this solved in rc36 compared to rc35?
j
No, we didn't have any stemming related fixes in rc36. Could you post the set of curl commands like in the gist I shared above into a Github issue, so we can investigate it further?