# Just Pushed: The revenge of CamelCase

**URL:** <https://discuss.elastic.co/t/just-pushed-the-revenge-of-camelcase/2941>\
**Category:** Elasticsearch\
**Created:** [May 8, 2010, 12:29am UTC](https://discuss.elastic.co/t/just-pushed-the-revenge-of-camelcase/2941 "2010-05-08T00:29:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [May 8, 2010, 12:29am UTC](https://discuss.elastic.co/t/just-pushed-the-revenge-of-camelcase/2941/1 "2010-05-08T00:29:16Z")

</div>

Hi,

Thanks to the new XContent abstraction, CamelCase are back. All JSON  
requests now support also CamelCase fields (such in the query DSL), and  
responses can be sent back in CamelCase fields with the addition of the  
`case` HTTP parameter (actually REST parameter) set to `camelCase`.

The main idea here is to support using DSLs in dynamic languages (such as  
Groovy) that use CamelCase as their naming convention. So, if you are using  
Groovy, for example, the query DSL can include "constantScore" as a query,  
on top of "constant\_score".

Note, this does not apply to the actual indexable source. The same JSON  
indexed will be returned, with the original casing.

cheers,  
shay.banon

---

<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, 4:24am UTC](https://discuss.elastic.co/t/just-pushed-the-revenge-of-camelcase/2941/2 "2017-07-06T04:24:13Z")

</div>