-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[FEATURE] Support missing DecayFunctions in FunctionScore
#7428
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
Comments
ScoreFunction
FunctionScore
Is there any way to, for example, inject manually written JSON into FunctionScore to make use of the decay functions, or is the realistic solution simply to use the 7.17.x client (as recommended in the project README), in the case where decay functions are required? |
@oscarlofwenhamn You can't pass arbitrary JSON to FunctionScore. If this is the only blocker to upgrade, you could consider dropping to the Transport layer (available from the client instance), where you can send a complete request as JSON and handle the JSON response. Sticking with 7.17.x in compatibility mode until this is available is also an option. |
Clear and concise, thanks! |
Is this still not adressed? |
@JanToreKyrdalen The code generator is currently being reworked to address this and other issues. A rough estimation for completion is end of Q1 2024. |
This comment was marked as spam.
This comment was marked as spam.
So, how's it going? It's been a year and three months from the original post, and 6 moths since Q1 2024 rough estimates. Any good news? |
Currently blocked until elastic/elasticsearch-specification#2545 is merged. |
Implemented in 8.14.4 |
Due to certain complexities with the
DecayFunction
union in the specification, the code generator is currently skipping these on theFunctionScore
container type, which prevents the use ofgauss
,exp
andlinear
functions. We need to solve this in the code generator so that these functions can be reintroduced in the 8.x client.Please update by adding a thumbs-up reaction to this comment if this is a blocker for you. This helps us prioritise the work on new features.
The text was updated successfully, but these errors were encountered: