Distance feature query: add support for numeric fields

[fbaligand]

Currently, Distance feature query deals only date and geo types. This would be great to also support numeric types (long, integer, ...).

For example, I currently use Elasticsearch to do geocoding. For this use case, ability to find the closest street number, compared to searched street number would be very interesting!

[elasticmachine]

Pinging @elastic/es-analytics-geo (:Analytics/Geo)

[elasticmachine]

Pinging @elastic/es-search (Team:Search)

[wchaparro]

This is a search issue, reassigning. Could this be done using runtime fields?

[fbaligand]

This is a search issue. But the aim of this issue is to enhanced « distance feature query », to support numeric fields, in plus of date and geopoint fields: https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-distance-feature-query.html

No relation with runtime fields.

[mayya-sharipova]

@fbaligand Thank you for submitting your request. We've discussed it within the team, and we found the provided use case to be quite unique, we haven't heard from other users asking for this. Also there is a way to implement this through script_score query, where you can design you own scoring formula based on field's numeric values.

We will still keep the issue open in case we hear more use cases, but currently we don't plan to implement it.

[fbaligand]

Sad to hear this, but thanks for the information.

[ulpcan]

While my date field can be consist of epoch seconds, type of long should be work too

It could be nice

[elasticsearchmachine]

Pinging @elastic/es-search-relevance (Team:Search Relevance)