-
Notifications
You must be signed in to change notification settings - Fork 8.4k
[ES|QL] Move functionality from RRF to FUSE #226743
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
Conversation
}); | ||
|
||
// ToDo:n Enable when RRF is on tech preview | ||
it.skip('suggests RRF immediately after a FORK command', async () => { | ||
// ToDo:n Enable when FUSE is on tech preview |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we ended up removing this restriction for FUSE - it does not have to always follow after FORK anymore.
up to you when you want to remove this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome 🙌 I did it here 2f21206
Thnx for letting me know
Pinging @elastic/kibana-esql (Team:ESQL) |
💚 Build Succeeded
Metrics [docs]Async chunks
Page load bundle
History
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
Summary
Just moves all our functionality from RRF to FUSE and removes the
after fork
rule as now it is supported everywhereRRF is going to be removed by the ES team