geo_point doesn't allow null values as of 1.1.0

[lusid]

After upgrading to 1.1.0, I found that my backend processes that perform bulk inserts/updates to ElasticSearch started failing with the following error:

MapperParsingException[failed to parse]; nested: ElasticsearchParseException[geo_point expected];

It seems that geo_point fields now require a non-null value for every document? Is there a way to bypass this behavior without having to change my ETL process to create fake geo_point coordinates?

[dadoonet]

Confirmed. I hit the same issue yesterday while moving some code from 1.0 to 1.1.

[dadoonet]

Pushed in 1.1, 1.x (1.2) and master branches.
1.0.2 is not affected by this issue.

[hkorte]

I had the same problem migrating from 1.0.1 to 1.1.0, but I noticed that you can have missing values, if you completely omit the geo_point field instead of having something like "field:{}" or "field:null". See this gist: https://gist.github.com/hkorte/9936192

[lusid]

You are probably right, as we do not include null value fields in our ETL process. However, our bulk updates do fail when the geo_point fields are left out of the bulk request.

[hossein761]

I just hit the same issue. Today I upgraded to 1.1. Should I wait for the next release for this fix? @dadoonet I got the 1.1 dependency today but this change is not there, i don't see it in the source code.

[dadoonet]

It will be in 1.1.1 which is not released yet. If you can't modify your injection, I guess you should wait for 1.1.1.

[d2kagw]

+1 on the issue.
We've been able to change our code to work around the issue, but looking forward to having it fixed.

[Tonkpils]

This still seems to be an issue in ES 1.7.1

[clintongormley]

@Tonkpils this works just fine in 1.7.1:

PUT t
{
  "mappings": {
    "t": {
      "properties": {
        "loc": {
          "type": "geo_point"
        }
      }
    }
  }
}

PUT t/t/1
{
  "loc": null
}

[Tonkpils]

You're right, it was an issue with the incoming parameters where Lon and lat were null. Apologies.