Cannot index using a specific ID

Elastic Enterprise Search App Search
#1

I tried to "Index Documents" with ID "4a343ca361d150e7-介護職".
It's seems Successful, but not appear in Documents.

Then, I tried to "Index Documents" with ID modified, here are the results.
"4a343ca361d150e7-介護" : appear in Documents (OK)
"4a343ca361d150e7--介護職" : appear in Documents (OK)
"a343ca361d150e7-介護職" : appear in Documents (OK)

What's wrong with ID "4a343ca361d150e7-介護職" ?

#2

Hey @YAHARA_RIV, I just tried to index a document with that ID and worked for me.

#3

Hello @JasonStoltz,

Thank you very much for trying and answering!

After writing the previous topic,
I tried to index a document with that ID using API (app-search-node) and got the same result.
I repeated it several times, but the result was the same.

Then I checked API's logs and found "Unable to save document" message.
What causes the "Unable to save document" message to be logged?

#4

What version of App Search are you using?

#5

Thank you for your reply!

I'm using App Search v7.9.0.
It runs in the Elastic Cloud.

#6

Great. And what language did you pick for the engine you are attempting to index into.

Can you try indexing with JUST the ID to confirm it's not caused by another field?

{
  "id": "4a343ca361d150e7-介護職"
}
#7

I created a 7.9 cluster on Cloud, created an engine with a Japanese language analyzer, and then indexed the document above with no issues.

I suggest you contact Elastic support directly and they can help you debug this further.

#8

Thank you for taking time for me.

As you might expect, I'm using an engine with a Japanese language analyzer.
I tried indexing with JUST the ID but the result was the same, so it's not caused by another field.

Then I created a NEW engine and indexed the document abobe (JUST the ID) and it was fine!
Apparently it's an engine-specific problem.
(But there are many indexed documents in the first engine, it's difficult to switch to the new engine...)

I'll contact Elastic support directly.
Thank you again!

#9

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.