Collection schema cannot contain a field with name id. Ignoring field about typesense HOT 7 CLOSED

This is an expected error, by design.

From the docs:

If the document contains an id field of type string, Typesense will use that field as the identifier for the document. Otherwise, Typesense will assign an auto-generated identifier to the document. Since it's a special field, the id field is not required to be defined as part of the collection schema.

from typesense.

Interesting, many thanks. One question: I've seen that before. But: why does this not happen when ID is not the beginning, as per searchable_id?

from typesense.

This is because only a field called id specifically is a special field. Other fields that end with _id are not automatically used as an id field and don't have any specific meaning inside of Typesense.

from typesense.

Alright, so "id_search" will always give this error and "search_id" won't. Thanks!

from typesense.

No, a field named id_search should not throw any errors in the logs, when mentioned in the schema.

from typesense.

No, a field named id_search should not throw any errors in the logs, when mentioned in the schema.

Interesting, but on 26.0 when I use id_search it gives an error and searchable_id for example does not.

from typesense.

Hmm, I don't see the same issue.

I used this gist to run Typesense. Then created a collection using a field called id_search and no errors were logged. Then created a field called id and the error was logged.

from typesense.