I always notice that the _id field of any index created is normaly a uuid, hash value or a simple numeric sucession depending of the use case.
My question is if there are any limitation in the form and aspect when choosing a custom _id beyond the be unique and avoid duplicates for a particular use case, for example related to throughput, or routing to shards.
_id field | Elasticsearch Guide [7.17] | Elastic goes into limitations on there, but it's really just;
_id is limited to 512 bytes in size and larger values will be rejected.
The content not matters in routing then?
As long as the id is unique the index will work correctly?
I dunno if they support all unicode, but otherwise, yes.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.