-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Sorting mixing "float" and "double" types doesn't work #78699
Comments
Pinging @elastic/es-search (Team:Search) |
@cbuescher is it okay if I pick this up? I want to contribute to ES, this seems to be a good starting point :) |
I think we first need to make sure we want to enable this. As I mentioned in the description, I'm not entirely sure if this doesn't work on purpose or if there are technical reasons that make this difficult to accomplish. Please take a look if you like but don't be disappointed if this moves into a different direction. |
Sure. Thanks for responding. |
I think this is relevant? #38095 |
I think we should handle mixing floating points transparently. It works for longs mixed with integers so I don't see why we wouldn't do the same for floats. |
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
Searching across multiple indices and sorting on a field that has a "double" type in one and a "float" type in other indices doesn't currently work:
Example script
This returns and exception with the following cause
I don't think we ever supported mixing these two types, at least on 6.8. the same error behaviour can be observed. However, mixing different numeric types of the short/integer/long family does word since we internally use the same
SortField.Type
for their NumericType, but for some reason the ones for "float" and "double" are different.Opening this issue to investigate whether this isn't possible for a good reason, simply technically infeasibel or if we can indeed add support for it.
The text was updated successfully, but these errors were encountered: