# How to generate \_id field manually **URL:** \ **Category:** Logstash\ **Created:** [July 8, 2020, 8:47am UTC](https://discuss.elastic.co/t/how-to-generate-id-field-manually/240302 "2020-07-08T08:47:10Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![Jenni](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jenni/32/29684_2.png) [@Jenni](https://discuss.elastic.co/u/Jenni)\ **Post date:** [July 9, 2020, 10:24am UTC](https://discuss.elastic.co/t/how-to-generate-id-field-manually/240302/8 "2020-07-09T10:24:02Z")
This is a constraint of SQL: > [@Is there a way to access internal \_id and \_type fields in ES SQL query (XPack)?](https://discuss.elastic.co/t/is-there-a-way-to-access-internal-id-and-type-fields-in-es-sql-query-xpack/174894/2): > > Hi @j_bennet, Indeed, this is not possible. The reason is that in SQL, an user is able to search for columns (fields) that they know about and that they actually inserted in Elasticsearch. But the \_id and the \_type are not fields/columns that you actually put in an index, this is more like meta information. And we bypass these fields in ES SQL by default. For \_id we have a [github issue](https://github.com/elastic/elasticsearch/issues/30266) created, but it's not on a concrete roadmap at the moment. Also, if I may, I'd like to comment on a stateme… --- _[View the full topic](https://discuss.elastic.co/t/how-to-generate-id-field-manually/240302)._