MapperParsingException - need help with dynamic property types

(pradeepjawahar) #1

I writing an application to index application logs into elastic search. I'm
having a problem when the type of a property changes in my data.
The following works fine

$ curl -XPOST http://localhost:9200/idx1/typ1 -d '

{"data": [

But when I try to index another data point I run into the following problem
$ curl -XPOST http://localhost:9200/idx1/typ1 -d '
{"error":"MapperParsingException[failed to parse [data]]; nested:
ElasticSearchIllegalArgumentException[unknown property [text]];

I understand that elastic search does not allow the type of a property to
be changed and that's causing the above Exception. I am usinn dynamic
mapping.Is there anyway I can circumvent this problem. I have tried the
following solutions :

  1. As suggested here to
    split my data.
  2. To use some kind of a filter so that elastic search always considers the
    field data to be an array of nested objects instead of an arrays of

The problem with the above two solutions are that I have several fields
which have the above characteristics and not all of them are known before
hand. So there could be a new field that's added to my data which behaves

My question is there a standard procedure to seal with such indexing
issues. Any help will be much appreciated. I am using 0.90.5 on a centos5

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
To view this discussion on the web visit
For more options, visit

(system) #2