-
Notifications
You must be signed in to change notification settings - Fork 24.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Distance feature query: add support for numeric fields #51804
Comments
Pinging @elastic/es-analytics-geo (:Analytics/Geo) |
Pinging @elastic/es-search (Team:Search) |
This is a search issue, reassigning. Could this be done using runtime fields? |
This is a search issue. No relation with runtime fields. |
@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. |
Sad to hear this, but thanks for the information. |
While my date field can be consist of epoch seconds, type of long should be work too It could be nice |
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!
The text was updated successfully, but these errors were encountered: