Mapping: index.mapping.ignore_malformed global index setting
#2220
Labels
Comments
martijnvg
added a commit
to martijnvg/elasticsearch
that referenced
this issue
Aug 31, 2012
…nded the ignore_malformed support to TTL, Ip and timestamp field types.
martijnvg
added a commit
that referenced
this issue
Aug 31, 2012
…e ignore_malformed support to TTL, Ip and timestamp field types.
|
Pushed @martijnvg changes. |
|
I didn't get it. |
|
they will be "stored" as the json is stored. They will not be indexed though so you can't search them. |
|
got it. so I can't also facet over them? |
|
only over the ones that ended up being indexed, not the "malformed" values. |
|
@kimchy Has this been brought into the latest stable release? (0.19.11 at time of comment) Also, am I correct in thinking that simply adding index.mapping.ignore_malformed to my elasticsearch.yml will allow me to take advantage of it? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add
index.mapping.ignore_malformedindex level setting that will automatically set it to all mappings (unless explicitly set).Original Request
Discussion is here: https://groups.google.com/forum/?fromgroups=#!topic/elasticsearch/Q4AL6rh0c3c
It would be nice to have a setting for object type fields with dynamic properties to ignore malformed values, i.e store them without raising an exception.
The text was updated successfully, but these errors were encountered: