Best strategy to handle dot in field names

Elastic Stack Elasticsearch
1

We are migrating from ES 2.4 to ES 6.x. In our initial tests we found that we have suppressed 'dot in field name' error in 2.4 by allowing them. Now we have indices with dot in field names and also the scenario where we have fields with name 'Status' and 'Status.Description' which is causing issue in 6.x. One approach seems to be replacing dot in field names with underscore but again there is a corner case where customer has fields like 'Status.Description' and 'Status_Description' already in their index.

Just wanted to understand if there is any other elegant way of handling these scenarios.

1 Like
2

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