# Как правильно работать с полями flattened в Kibana?

**URL:** <https://discuss.elastic.co/t/flattened-kibana/280232>\
**Category:** Вопросы на русском языке\
**Created:** [August 2, 2021, 2:55pm UTC](https://discuss.elastic.co/t/flattened-kibana/280232 "2021-08-02T14:55:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sergei\_Frolov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sergei_frolov/32/47922_2.png) [@Sergei\_Frolov](https://discuss.elastic.co/u/Sergei_Frolov)\
**Post date:** [August 2, 2021, 2:55pm UTC](https://discuss.elastic.co/t/flattened-kibana/280232/1 "2021-08-02T14:55:20Z")

</div>

Приветствую! Подскажите, как правильно работать с полями flattened в Kibana? Есть ли какая-то возможность подсветки при поиске - как сейчас делается для других полей? Может еще есть какие-то практики, как удобно с ними работать? Сейчас пока я не нашел ничего кроме вычисляемых полей в Kibana для работы с ними.

---

<div class="post-metadata">

**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\
**Post date:** [August 2, 2021, 3:38pm UTC](https://discuss.elastic.co/t/flattened-kibana/280232/2 "2021-08-02T15:38:37Z")

</div>

> <https://github.com/elastic/kibana/issues/25820>
>
> A new object field type is \[coming to ES\](https://github.com/elastic/elasticsear…ch/issues/33003). I played around with the feature branch a bit today and collected some thoughts and findings. From what I've seen so far, there are some small updates to Kibana we'll definitely want to make and some things we should discuss.
> 
> \* Need to add \`JSON\` type to kibana (or whatever name the ES lands on for this field type). Currently it shows up in the index pattern as \`unknown\`.
> \* Autocomplete on values doesn't work because the field is not aggregatable
> \* Autocomplete on field names doesn’t work, because we don't know what sub-fields the object has
> \* In KQL we implement wildcard field names ourselves based on the fields in the index pattern, so something like head\*:application/json actually works but headers.con\*:application/json does not because we don’t know about those fields. This could be pretty confusing to users
> \* Filters can’t be created from the doc table (similar to our treatment of arrays of objects today)
> \* Filters can't be created from the "Add Filter" UI in the filter bar (this is worse than no autocomplete in the query bar because we don’t allow free text input for the field name. Currently the field name must be in the index pattern)
> \* Highlighting would be nice, however we don’t currently highlight values inside arrays of objects, so a lack highlighting in a JSON document won’t be totally surprising to current users.
> 
> I only spent about an hour with it so there may be more things I'm missing, would definitely be good to get more eyes on it.
> 
> Feature branch here if anyone else wants to check it out: https://github.com/elastic/elasticsearch/tree/object-fields

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 30, 2021, 3:39pm UTC](https://discuss.elastic.co/t/flattened-kibana/280232/3 "2021-08-30T15:39:26Z")

</div>

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