Japanese Kanji cannot search

[exkoi]

Describe the bug
Japanese Kanji cannot search

To Reproduce
Create Index:

curl -X POST 'http://localhost:7700/indexes' \
  -H 'Content-Type: application/json' \
  --data-binary '{
    "uid": "hospitals",
    "primaryKey": "id"
  }'

Setting index:

curl -X PATCH 'http://localhost:7700/indexes/hospitals/settings' \
  -H 'Content-Type: application/json' \
  --data-binary '{
    "searchableAttributes": [
      "name",
      "kana"
    ],
    "displayedAttributes": [
      "name",
      "kana"
    ]
  }'

Insert documents:

curl -X POST 'http://localhost:7700/indexes/hospitals/documents' \
  -H 'Content-Type: application/json' \
  --data-binary '[
      { "id": 1, "name": "日健クリニック", "kana": "ニッケンクリニック" },
      { "id": 2, "name": "日見中央病院", "kana": "ヒミチュウオウビョウイン" }
  ]'

Expected behavior
When search for the word "健", I want "日健クリニック" to be hit, but documents containing "見" are hit.
In Japanese, "健" and "見" both have the same pronunciation as "ken", but they have different meanings.

Screenshots

Meilisearch version:
v1.7.2

Additional context
Docker Image: getmeili/meilisearch:v1.7

[uintaam]

This is because Meilisearch defaults to Chinese support. I have the same issue #4162

You can use the Japanese builds to solve your problem #3882

[exkoi]

This is because Meilisearch defaults to Chinese support. I have the same issue #4162

You can use the Japanese builds to solve your problem #3882

@uintaam Thank you for your reply!
Can I use Japanese build without Docker? (I use Ubuntu22.04 without Docker in production)

[curquiza]

Hello @exkoi, two solutions

• compile from source. See the related docs ("Source tab"). But instead of cargo build --release, use this command: cargo build --release -p meilisearch -p meilitool --no-default-features --features "analytics mini-dashboard japanese"
• or, if you don't want to bother with this, you can also use our cloud offer and ask support team (in the chat box) to use Japanese version

[exkoi]

Thank you @curquiza !
I'll try your solution

[curquiza]

I'm closing this issue since we have another opened 😊