[Maps] Move sort out of top hits configuration

[nreese]

#46882 requests for sorting top hits by number fields instead of time fields. As I started to look into the implementation it occurred to me, "Hey, why do we bury sort input under top hits? Won't users want to sort regular searches as well"

Implementing #46882 will require a saved object migration because the sort state is stored in a field called topHitsTimeField. That name is not generic enough to support numbers. As long as I have to change the name, why not just change it to sortField and move the sort UI out of top hits and let users to sort all Elasticsearch documents, not just those with top hits?

Thoughts?

[elasticmachine]

Pinging @elastic/kibana-gis (Team:Geo)

[bcamper]

Sounds reasonable. How else would a general sorting parameter affect the map results, outside of the "top hits" option?

• If the # of results is limited by query limit (sorting is a bandaid to return most relevant results, but hoping we eliminate this one anyway).
• For visual sorting top-to-bottom on the map? This would be genuinely useful to have control over.
• Any others?

I'd also like us to be mindful of not giving the user too many choices up front. But that also can be solved more generally by moving some options to Advanced (for example) in the future.

[nreese]

I'd also like us to be mindful of not giving the user too many choices up front

I think we already do a good job of this. When you create a layer, the only options are index pattern and geo field. All of these other options are only visible when editing a layer so users get to see dots a on a a map before getting presented with too many inputs

[bcamper]

@nreese is my assumption about the sorting affecting visual ordering accurate?

[nreese]

yes, the items are visualized in the order they are returned

[thomasneirynck]

Closed by #47361