Closed ppf2 closed 9 years ago
body_text vs bodyText vs BodyText too?
On Fri, Nov 21, 2014 at 3:52 PM, Pius notifications@github.com wrote:
We currently have a dynamic strict setting that prevents the automatic creation of fields within a type.
Would be nice to provide an additional option which allows for the dynamic creation of fields within a type, but disallow dynamic creation of the same field but with a different casing (eg. "body" vs. "Body")
— Reply to this email directly or view it on GitHub https://github.com/elasticsearch/elasticsearch/issues/8602.
Yah not quite sure about the body_text scenario, but for bodytext,Bodytext,bodyText,BodyText, certainly for this use case. Thx.
Meh I don't like this at all. It introduces so many problems elsewhere. Field names are case sensitive, and that's that. Problems like this should be handled on the application side.
Sorry, but I'm closing this.
We currently have a dynamic strict setting that prevents the automatic creation of fields within a type.
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-dynamic-mapping.html#mapping-dynamic-mapping
Would be nice to provide an additional option which allows for the dynamic creation of fields within a type, but disallow dynamic creation of the same field but with a different casing (eg. "body" vs. "Body")