# Long \_id (so \_uid) field performance issues? **URL:** \ **Category:** Elasticsearch\ **Created:** [July 3, 2014, 3:59pm UTC](https://discuss.elastic.co/t/long--id-so--uid-field-performance-issues/18466 "2014-07-03T15:59:36Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![James\_Campbell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james_campbell/32/1411_2.png) [@James\_Campbell](https://discuss.elastic.co/u/James_Campbell)\ **Post date:** [July 3, 2014, 3:59pm UTC](https://discuss.elastic.co/t/long--id-so--uid-field-performance-issues/18466/1 "2014-07-03T15:59:36Z")
Hello-- I am currently working with a document model that requires updates, and so am using customized values for the \_id field to ensure I can appropriately access documents in the future. I have not discovered any performance issues yet. Are there any limitations on the \_id fields, in terms of performance or otherwise (e.g. actual field length limits) that I should be aware of as I pursue this model? James Campbell -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/b6d88116-8507-4979-a2a9-4efe15a2adec%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/b6d88116-8507-4979-a2a9-4efe15a2adec%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:18am UTC](https://discuss.elastic.co/t/long--id-so--uid-field-performance-issues/18466/2 "2017-07-06T01:18:05Z")