[Discover] Sort by fieldname of nested fields.

[tmitanitky]

When expanding a document in Discover, non-nested fields are sorted by their field names.
When toggling the field details of a nested field, however, the fields in the nested field are not sorted by their names. Since the order is the same across all documents, it is assumed to reflect some internal order.

It would be helpful to find a specific field if the fields in nested field were sorted and displayed.

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[timroes]

Just for clarification: Do you mean inside the "Table" tab or inside the "JSON" tab of a document?

[tmitanitky]

I intended inside the "Table" tab.
Now I checked to find the order in the "JSON" tab seems to be the same as that of the Table tab.

[majagrubic]

Is this referring to nested fields or multi-fields? What does "order is the same across all documents" mean?

[majagrubic]

Also, we truncate the display of nested fields, so in a case of a many items in an array with a lot of properties, you still wouldn't be able to see much, unless you go to the JSON view.

Eg. table view:

vs JSON view of the same document:

so I'm not sure how beneficial this would be. Maybe I'm missing something.

[tmitanitky]

Referring to nested fields. I'm sorry it's unclear.

I attach sample images. These are from "Table" tabs of "Expanded document" in "Discovery" and toggled the details.

The displayed order of nested fields are not sorted. ('RXE' comes in the 4th place and again in the 7th place apartly. If sorted, the displayed order might be [ORC.Enter.. ORC.Enter, ORC.Place, RXE.Dispense, RXE.Give.., TQ1.Service.., TQ1.SetId..])
"Order is the same across all documents" means that the unsorted order for some reason seems to be common among documents in the index. (The orders are same in different documents)

If it is sorted, it will be easier to find a specific field, especially when there is multi-level nesting like this.

Thanks

[tmitanitky]

The order is also not sorted in JSON tab.

[majagrubic]

After having a look at this, I think this would be best implemented on an index pattern, in one of the formatters. Going to pass this on to @elastic/kibana-app-services for their opinion on this.