Problem when there is a field called "geo"

Elastic Stack Elasticsearch
1

hi,

i am not sure if this is already known, if yes, sorry for the
doubleposting, but i could not find anything.

we are using version 0.16.2 and today we detected the following
problem: we added to our items in elasticsearch a field called "geo"
that contains this data:

"geo":{"address_components":
[{"long_name":"2B","short_name":"2B","types":["street_number"]},
{"long_name":"Somewhere","short_name":"Somewhere","types":["route"]},
{"long_name":"Somewhere","short_name":"Somewhere","types":
["sublocality","political"]},
{"long_name":"Somewhere","short_name":"Somewhere","types":
["locality","political"]},
{"long_name":"Somewhere","short_name":"Wien","types":
["administrative_area_level_1","political"]},
{"long_name":"\u00d6sterreich","short_name":"AT","types":
["country","political"]},
{"long_name":"1030","short_name":"1030","types":
["postal_code"]}],"formatted_address":"Somewhere","geometry":
{"location":{"lat":48.1934556,"lng":
16.3966855},"location_type":"ROOFTOP"},"types":["street_address"]}

which is a reduced google location result.

when i try to add stuff to items in elasticsearch after this geo-field
is present, new fields are ignored in searches. they are present in
the "_source", but i cannot search for them (not even with a filter
for "exists").

as soon as i rename the "geo"-field for example to "geolocation", it
works fine again, i can search for new fields without any problem.

any ideas why?

thank you,
Max

2

That should not be hte case, can you gist a curl repro?

On Friday, July 1, 2011 at 10:22 AM, Max Kossatz wrote:

hi,

i am not sure if this is already known, if yes, sorry for the
doubleposting, but i could not find anything.

we are using version 0.16.2 and today we detected the following
problem: we added to our items in elasticsearch a field called "geo"
that contains this data:

"geo":{"address_components":
[{"long_name":"2B","short_name":"2B","types":["street_number"]},
{"long_name":"Somewhere","short_name":"Somewhere","types":["route"]},
{"long_name":"Somewhere","short_name":"Somewhere","types":
["sublocality","political"]},
{"long_name":"Somewhere","short_name":"Somewhere","types":
["locality","political"]},
{"long_name":"Somewhere","short_name":"Wien","types":
["administrative_area_level_1","political"]},
{"long_name":"\u00d6sterreich","short_name":"AT","types":
["country","political"]},
{"long_name":"1030","short_name":"1030","types":
["postal_code"]}],"formatted_address":"Somewhere","geometry":
{"location":{"lat":48.1934556,"lng":
16.3966855},"location_type":"ROOFTOP"},"types":["street_address"]}

which is a reduced google location result.

when i try to add stuff to items in elasticsearch after this geo-field
is present, new fields are ignored in searches. they are present in
the "_source", but i cannot search for them (not even with a filter
for "exists").

as soon as i rename the "geo"-field for example to "geolocation", it
works fine again, i can search for new fields without any problem.

any ideas why?

thank you,
Max

3

hi,

sorry, was on vacation, thats why it took me so long to answer :slight_smile:

we have an elasticsearch-db with around 11 million documents (around
100GB of data) there we saw this problem. i tried to reporduce it with
an empty database (same 0.16.2 version) and was not able to reproduce
the problem, really strange, any idea how i can give you infos about
this problem?

thank you, great work!

MAX

On 1 Jul., 11:10, Shay Banon shay.ba...@elasticsearch.com wrote:

That should not be hte case, can you gist a curl repro?

On Friday, July 1, 2011 at 10:22 AM, Max Kossatz wrote:

hi,

i am not sure if this is already known, if yes, sorry for the
doubleposting, but i could not find anything.

we are using version 0.16.2 and today we detected the following
problem: we added to our items in elasticsearch a field called "geo"
that contains this data:

"geo":{"address_components":
[{"long_name":"2B","short_name":"2B","types":["street_number"]},
{"long_name":"Somewhere","short_name":"Somewhere","types":["route"]},
{"long_name":"Somewhere","short_name":"Somewhere","types":
["sublocality","political"]},
{"long_name":"Somewhere","short_name":"Somewhere","types":
["locality","political"]},
{"long_name":"Somewhere","short_name":"Wien","types":
["administrative_area_level_1","political"]},
{"long_name":"\u00d6sterreich","short_name":"AT","types":
["country","political"]},
{"long_name":"1030","short_name":"1030","types":
["postal_code"]}],"formatted_address":"Somewhere","geometry":
{"location":{"lat":48.1934556,"lng":
16.3966855},"location_type":"ROOFTOP"},"types":["street_address"]}

which is a reduced google location result.

when i try to add stuff to items in elasticsearch after this geo-field
is present, new fields are ignored in searches. they are present in
the "_source", but i cannot search for them (not even with a filter
for "exists").

as soon as i rename the "geo"-field for example to "geolocation", it
works fine again, i can search for new fields without any problem.

any ideas why?

thank you,
Max

4

No, sounds strange... . Can you use get mapping API and verify that geo is
mapped correctly maybe?

On Tue, Jul 19, 2011 at 12:57 PM, Max Kossatz max.kossatz@gmail.com wrote:

hi,

sorry, was on vacation, thats why it took me so long to answer :slight_smile:

we have an elasticsearch-db with around 11 million documents (around
100GB of data) there we saw this problem. i tried to reporduce it with
an empty database (same 0.16.2 version) and was not able to reproduce
the problem, really strange, any idea how i can give you infos about
this problem?

thank you, great work!

MAX

On 1 Jul., 11:10, Shay Banon shay.ba...@elasticsearch.com wrote:

That should not be hte case, can you gist a curl repro?

On Friday, July 1, 2011 at 10:22 AM, Max Kossatz wrote:

hi,

i am not sure if this is already known, if yes, sorry for the
doubleposting, but i could not find anything.

we are using version 0.16.2 and today we detected the following
problem: we added to our items in elasticsearch a field called "geo"
that contains this data:

"geo":{"address_components":
[{"long_name":"2B","short_name":"2B","types":["street_number"]},
{"long_name":"Somewhere","short_name":"Somewhere","types":["route"]},
{"long_name":"Somewhere","short_name":"Somewhere","types":
["sublocality","political"]},
{"long_name":"Somewhere","short_name":"Somewhere","types":
["locality","political"]},
{"long_name":"Somewhere","short_name":"Wien","types":
["administrative_area_level_1","political"]},
{"long_name":"\u00d6sterreich","short_name":"AT","types":
["country","political"]},
{"long_name":"1030","short_name":"1030","types":
["postal_code"]}],"formatted_address":"Somewhere","geometry":
{"location":{"lat":48.1934556,"lng":
16.3966855},"location_type":"ROOFTOP"},"types":["street_address"]}

which is a reduced google location result.

when i try to add stuff to items in elasticsearch after this geo-field
is present, new fields are ignored in searches. they are present in
the "_source", but i cannot search for them (not even with a filter
for "exists").

as soon as i rename the "geo"-field for example to "geolocation", it
works fine again, i can search for new fields without any problem.

any ideas why?

thank you,
Max