Using a colon in a field name does not work?

I have the following as part of my mapping file:

"entities.name1:Name2": {
       "type": "nested"

But the field does not actually end up nested in the index.

Is there a problem with the use of colons as part of a field name? Would I need to escape the colon in JSON string to make it work?

It turns out the reason must have been somewhere else, at some point it suddenly worked as expected. So the fact of the matter seems to be that the colon needs to get escaped in Kibana (which is annoying), but not in the mappings file or in the actual ES requests.

1 Like

Thanks for sharing that, and apologies for my post, it was for another topic!

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