Currently, the flattened field type does not allow keys to contain the \0 character. This is because the field type uses \0 internally as a separator. Some users use flattened with messy data that's outside their control, and run into this restriction. Here's an example from the transform feature, which adds the result of a terms aggregation to a flattened field: #75875.
Maybe we could consider adding automatic escaping in flattened to avoid this restriction.
Currently, the
flattened
field type does not allow keys to contain the\0
character. This is because the field type uses\0
internally as a separator. Some users useflattened
with messy data that's outside their control, and run into this restriction. Here's an example from the transform feature, which adds the result of a terms aggregation to aflattened
field: #75875.Maybe we could consider adding automatic escaping in
flattened
to avoid this restriction.