# Upgraded to 8.2 and datastream, geo\_point set as and stuck as string in data view **URL:** \ **Category:** Kibana\ **Created:** [June 10, 2022, 8:59pm UTC](https://discuss.elastic.co/t/upgraded-to-8-2-and-datastream-geo-point-set-as-and-stuck-as-string-in-data-view/306916 "2022-06-10T20:59:03Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![JSkier](https://avatars.discourse-cdn.com/v4/letter/j/e47c2d/32.png) [@JSkier](https://discuss.elastic.co/u/JSkier)\ **Post date:** [June 10, 2022, 8:59pm UTC](https://discuss.elastic.co/t/upgraded-to-8-2-and-datastream-geo-point-set-as-and-stuck-as-string-in-data-view/306916/1 "2022-06-10T20:59:04Z")
I upgraded my cluster to 8.2 last week, and started migrating over to data streams for filebeat, metricbeat, and logstash. For the most part this went okay, with the exception of geo\_points. Initially, the _geo_ object was added for some reason, so I updated the index template to account for that. Running into an issue where the data stream, even though mapped as a geo\_point from a logstash instance, is picked up as a keyword, and therefore does not allow mapping. In conclusion, logstash instructs it to be a geo\_point, and the index template for the stream is mapped as a geo\_point, but that's not what is getting indexed. Kibana shows it as a keyword: ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/3/33186ac2bf660961899e385c6a12bbc8cd38bacd.png) Any ideas as to what I am missing? ---
**Author:** ![JSkier](https://avatars.discourse-cdn.com/v4/letter/j/e47c2d/32.png) [@JSkier](https://discuss.elastic.co/u/JSkier)\ **Post date:** [June 17, 2022, 4:02pm UTC](https://discuss.elastic.co/t/upgraded-to-8-2-and-datastream-geo-point-set-as-and-stuck-as-string-in-data-view/306916/2 "2022-06-17T16:02:42Z")
Still an issue. Keeping open, will also put in a ticket with support. ---
**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\ **Post date:** [June 17, 2022, 6:28pm UTC](https://discuss.elastic.co/t/upgraded-to-8-2-and-datastream-geo-point-set-as-and-stuck-as-string-in-data-view/306916/3 "2022-06-17T18:28:19Z")
@Nathan_Reese / @jsanz Thanks, Bhavya ---
**Author:** ![jsanz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsanz/32/53734_2.png) [@jsanz](https://discuss.elastic.co/u/jsanz)\ **Post date:** [June 18, 2022, 12:42pm UTC](https://discuss.elastic.co/t/upgraded-to-8-2-and-datastream-geo-point-set-as-and-stuck-as-string-in-data-view/306916/4 "2022-06-18T12:42:10Z")
@JSkier could you confirm the actual mapping of your data stream contains the correct geo\_point field ? I'm not very familiar with data streams details but we have a tutorial that uses them > **[Track, visualize, and alert on assets in real time | Kibana Guide \[8.2\] |...](https://www.elastic.co/guide/en/kibana/current/asset-tracking-tutorial.html)** > > Add interactive capabilities to your dashboard, such as controls that allow you to apply dashboard-level filters, and drilldowns that allow you to navigate to other dashboards and external websites. Maybe you could take a look in case you notice any difference with your setup? Sorry for not being much specific right now but maybe this helps to unlock the issue. ---
**Author:** ![jsanz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsanz/32/53734_2.png) [@jsanz](https://discuss.elastic.co/u/jsanz)\ **Post date:** [June 20, 2022, 2:32pm UTC](https://discuss.elastic.co/t/upgraded-to-8-2-and-datastream-geo-point-set-as-and-stuck-as-string-in-data-view/306916/5 "2022-06-20T14:32:21Z")
Also, check this thread šŸ‘‡ and in particular the solution comment in case you are hitting the same issue > [@Map data not displaying in 8.2.0](https://discuss.elastic.co/t/map-data-not-displaying-in-8-2-0/307450/18): > > HI, I found what the problem is. I'm not 100% sure when the change was introduced, possibly 7.17 but if you don't set ecs\_compatibility =\> disabled in your logstash file(filter) you will have conflicting mappings. Basically you end up with mixture of ECS geo mappings and your existing defined mappings. To resolve this: filter { geoip { source =\> "[host][ip]" ecs\_compatibility =\> disabled } } Ref: https://www.elastic.co/guide/en/logstash/7.17/ecs-ls.htmlhttps://www.elastic.co/gā€¦ ---
**Author:** ![JSkier](https://avatars.discourse-cdn.com/v4/letter/j/e47c2d/32.png) [@JSkier](https://discuss.elastic.co/u/JSkier)\ **Post date:** [June 20, 2022, 6:25pm UTC](https://discuss.elastic.co/t/upgraded-to-8-2-and-datastream-geo-point-set-as-and-stuck-as-string-in-data-view/306916/6 "2022-06-20T18:25:55Z")
Looks promising, I will check tomorrow and see if the config change will work. Looking at data streams some more, it would appear that mapping syntax may be slightly different, which may be contributing to my issues. If the first problem doesn't resolve this, I will dig in some more to the syntax of the mapped fields some more. Will post my findings, thank you for your help! ---
**Author:** ![JSkier](https://avatars.discourse-cdn.com/v4/letter/j/e47c2d/32.png) [@JSkier](https://discuss.elastic.co/u/JSkier)\ **Post date:** [June 21, 2022, 2:40pm UTC](https://discuss.elastic.co/t/upgraded-to-8-2-and-datastream-geo-point-set-as-and-stuck-as-string-in-data-view/306916/7 "2022-06-21T14:40:34Z")
The geoip plugin still works with ecs compat disabled, however now the coordinate field just isn't there in new data. So, fields like Region and Continent still work, sans the coordinate field now. Looking at the data stream template, it looks fine, and appears in line with this: [Change mappings and settings for a data stream | Elasticsearch Guide [8.2] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/data-streams-change-mappings-and-settings.html) No word from support yet. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 19, 2022, 2:40pm UTC](https://discuss.elastic.co/t/upgraded-to-8-2-and-datastream-geo-point-set-as-and-stuck-as-string-in-data-view/306916/8 "2022-07-19T14:40:54Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.