# Dealing with dots in fields for the 2.0 upgrade **URL:** \ **Category:** Elasticsearch\ **Created:** [November 13, 2015, 8:57pm UTC](https://discuss.elastic.co/t/dealing-with-dots-in-fields-for-the-2-0-upgrade/34562 "2015-11-13T20:57:01Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![shanec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shanec/32/4004_2.png) [@shanec](https://discuss.elastic.co/u/shanec)\ **Post date:** [November 14, 2015, 1:40am UTC](https://discuss.elastic.co/t/dealing-with-dots-in-fields-for-the-2-0-upgrade/34562/2 "2015-11-14T01:40:41Z")
Man I wish I could tell you this were easier. First a moment of background. From a Logstash perspective, Aaron wrote a stickied post over [here](https://discuss.elastic.co/t/please-read-upgrading-logstash-and-elasticsearch-to-2-0/33791) about it. They added a ['de\_dot' filter](https://www.elastic.co/blog/introducing-the-de_dot-filter) to help with situations where you may not have control over the source fields. Dots in field names also caused problems in [Kibana](https://github.com/elastic/kibana/issues/3540). And they could cause really weird problems with field ambiguity, as seen [here](https://github.com/elastic/elasticsearch/issues/11337). Ugh... what a mess ever allowing them caused. I know none of that helps your current situation, because the unfortunate answer is you're going to have to reindex. This is one of those breaking changes that just had to happen. We looked into ways to simplify the process to avoid a reindex or do it in place, but the options just weren't tenable unfortunately. A few of the elasticsearch clients do have "reindex" functions built in. I've written [this script](https://github.com/eskibars/de-dot) which uses the perl reindex API, which you can see as an example. --- _[View the full topic](https://discuss.elastic.co/t/dealing-with-dots-in-fields-for-the-2-0-upgrade/34562)._