# YAML as first class citizen for more operations?

**URL:** <https://discuss.elastic.co/t/yaml-as-first-class-citizen-for-more-operations/13940>\
**Category:** Elasticsearch\
**Created:** [October 14, 2013, 12:58pm UTC](https://discuss.elastic.co/t/yaml-as-first-class-citizen-for-more-operations/13940 "2013-10-14T12:58:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Oliver\_B\_Fischer](https://avatars.discourse-cdn.com/v4/letter/o/f04885/32.png) [@Oliver\_B\_Fischer](https://discuss.elastic.co/u/Oliver_B_Fischer)\
**Post date:** [October 14, 2013, 12:58pm UTC](https://discuss.elastic.co/t/yaml-as-first-class-citizen-for-more-operations/13940/1 "2013-10-14T12:58:28Z")

</div>

Currently YAML can be only used for index configuration. But wouldn't it  
be helpful to allow also to index YAML documents and to allow us to  
write our mappings and queries also in YAML?

JSON is great but if your mapping is longer than the usual examples you  
get lost in { and }.

So, why not making YAML a first class citzien of ElasticSearch?

BYe,

Oliver

--  
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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**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, 2:12am UTC](https://discuss.elastic.co/t/yaml-as-first-class-citizen-for-more-operations/13940/2 "2017-07-06T02:12:35Z")

</div>