# Eshadoop : why lowercasing field names? **URL:** \ **Category:** Elasticsearch\ **Created:** [February 15, 2015, 1:09am UTC](https://discuss.elastic.co/t/eshadoop-why-lowercasing-field-names/22170 "2015-02-15T01:09:57Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Ulul](https://avatars.discourse-cdn.com/v4/letter/u/71c47a/32.png) [@Ulul](https://discuss.elastic.co/u/Ulul)\ **Post date:** [February 15, 2015, 1:09am UTC](https://discuss.elastic.co/t/eshadoop-why-lowercasing-field-names/22170/1 "2015-02-15T01:09:57Z")
Hi I'm a (rather impressed) user of eshadoop but I'm a bit puzzled by the fact that all field names are lowercased prior to being sent to es and the doc doc states : "Elasticsearch accepts only lower-case field name and, as such, elasticsearch-hadoop will always convert Pig column names to lower-case." [http://www.elasticsearch.org/guide/en/elasticsearch/hadoop/current/pig.html](http://www.elasticsearch.org/guide/en/elasticsearch/hadoop/current/pig.html) es is perfectly fine with uppercase in field names (not in indices, but in fields it's fine). This is no big deal, but I'm curious of the explanation, to make sure I'm not missing something Thanks (both for help and nice software) Ulul -- 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/54DFF1E5.4020900%40ulul.org](https://groups.google.com/d/msgid/elasticsearch/54DFF1E5.4020900%40ulul.org). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![costin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/costin/32/44950_2.png) [@costin](https://discuss.elastic.co/u/costin)\ **Post date:** [February 15, 2015, 10:50am UTC](https://discuss.elastic.co/t/eshadoop-why-lowercasing-field-names/22170/2 "2015-02-15T10:50:56Z")
Hi, Actually the documentation is incorrect. The problem lies mainly with Hive who treat field names as case insensitive. In Pig the behavior was inconsistent, depending on the version and the script used. Hence why using the mapping feature is recommended. However, the doc needs to be corrected. On 2/15/15 3:09 AM, Ulul wrote: > Hi > I'm a (rather impressed) user of eshadoop but I'm a bit puzzled by the fact that all field names are lowercased prior to > being sent to es and the doc doc states : "Elasticsearch accepts only lower-case field name and, as such, > elasticsearch-hadoop will always convert Pig column names to lower-case." > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/hadoop/current/pig.html) > > es is perfectly fine with uppercase in field names (not in indices, but in fields it's fine). > This is no big deal, but I'm curious of the explanation, to make sure I'm not missing something > > Thanks (both for help and nice software) > > Ulul -- Costin -- 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/54E07A10.5020006%40gmail.com](https://groups.google.com/d/msgid/elasticsearch/54E07A10.5020006%40gmail.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, 12:32am UTC](https://discuss.elastic.co/t/eshadoop-why-lowercasing-field-names/22170/3 "2017-07-06T00:32:44Z")