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.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.