# Problem when there is a field called "geo" **URL:** \ **Category:** Elasticsearch\ **Created:** [July 1, 2011, 7:22am UTC](https://discuss.elastic.co/t/problem-when-there-is-a-field-called-geo/4749 "2011-07-01T07:22:27Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Max\_Kossatz](https://avatars.discourse-cdn.com/v4/letter/m/b9bd4f/32.png) [@Max\_Kossatz](https://discuss.elastic.co/u/Max_Kossatz)\ **Post date:** [July 1, 2011, 7:22am UTC](https://discuss.elastic.co/t/problem-when-there-is-a-field-called-geo/4749/1 "2011-07-01T07:22:27Z")
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 ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [July 1, 2011, 9:10am UTC](https://discuss.elastic.co/t/problem-when-there-is-a-field-called-geo/4749/2 "2011-07-01T09:10:31Z")
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 ---
**Author:** ![Max\_Kossatz](https://avatars.discourse-cdn.com/v4/letter/m/b9bd4f/32.png) [@Max\_Kossatz](https://discuss.elastic.co/u/Max_Kossatz)\ **Post date:** [July 19, 2011, 9:57am UTC](https://discuss.elastic.co/t/problem-when-there-is-a-field-called-geo/4749/3 "2011-07-19T09:57:18Z")
hi, sorry, was on vacation, thats why it took me so long to answer 🙂 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](mailto: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 ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [July 19, 2011, 9:40pm UTC](https://discuss.elastic.co/t/problem-when-there-is-a-field-called-geo/4749/4 "2011-07-19T21:40:00Z")
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](mailto:max.kossatz@gmail.com) wrote: > hi, > > sorry, was on vacation, thats why it took me so long to answer 🙂 > > 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](mailto: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 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 4:00am UTC](https://discuss.elastic.co/t/problem-when-there-is-a-field-called-geo/4749/5 "2017-07-06T04:00:07Z")