Geo_point type doesn't match

Elastic Stack Elasticsearch
1

Hello,

I have an issue with geo_point mapping, it does'nt apply ! geo_server_ip.location has a "number" type insted of "geo_point". :unamused:

My logstash filter:

geoip {
add_tag => [ "GeoIP" ]
source => "server_ip"
target => "geo_server_ip"
}

my Elastic template:

"mappings": {
"logs": {
"properties": {
"geo_server_ip": {
"dynamic": true,
"type": "object",
"properties": {
"timezone": {
"type": "string"
},
"ip": {
"index": "not_analyzed",
"type": "ip",
"doc_values": true
},
"latitude": {
"type": "double"
},
"continent_code": {
"type": "string"
},
"city_name": {
"index": "not_analyzed",
"type": "string"
},
"country_code2": {
"type": "string"
},
"country_name": {
"index": "not_analyzed",
"type": "string"
},
"location": {
** "type": "geo_point"**
},
...

This is my fileds and mapping:

Any ideas about this case ?

2

Hey,

is there an index template for your index naming scheme that configures this appropriately? logstash ships with a standard template, which is only applied for logstash- indices... if you renamed you indexes this template will not be applied and you have to put your own.

--Alex

3

Hello,

This case is resolved, mapping correctly match on april..
I have to reindex in order avoid conflict mapping.

(index-2017.03 location:float and on index-2017.04 location:geo_point)

Thanks.

4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.