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
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
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
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
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.