We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What do you want to do?
Tell us about your request. Provide a summary of the request.
Page https://opensearch.org/docs/2.15/search-plugins/sql/ppl/functions/, under "eval", reads: "The eval command is not rewritten to OpenSearch DSL, it is only executed on the coordination node."
That is a description of the implementation which is meaningless to most users. What does this mean for the user?
*Version: List the OpenSearch version to which this issue applies, e.g. 2.14, 2.12--2.14, or all.
2.15
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
The text was updated successfully, but these errors were encountered:
Thanks, @smacrakis, it looks like that sentence is used for all commands. @kolchfa-aws, do you know what is meant by this statement?
Sorry, something went wrong.
Maybe there are performance implications? @penghuo could you clarify if and why this limitation is important to the users?
No branches or pull requests
What do you want to do?
Tell us about your request. Provide a summary of the request.
Page https://opensearch.org/docs/2.15/search-plugins/sql/ppl/functions/, under "eval", reads: "The eval command is not rewritten to OpenSearch DSL, it is only executed on the coordination node."
That is a description of the implementation which is meaningless to most users. What does this mean for the user?
*Version: List the OpenSearch version to which this issue applies, e.g. 2.14, 2.12--2.14, or all.
2.15
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
The text was updated successfully, but these errors were encountered: