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
Is your feature request related to a problem? We are migrating from elasticsearch to opensearch and could not migrate many queries as they are using runtimefields https://www.elastic.co/guide/en/elasticsearch/reference/current/sql-runtime-fields.html , also see related issues where work around using SQL does not work #2320
What solution would you like? allow users to specify scripted fields for SQL query when using API
What alternatives have you considered? We tried using nested SQL query , but got various errors such as missing field, join related
Do you have any additional context? https://www.elastic.co/guide/en/elasticsearch/reference/current/sql-runtime-fields.html
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem?
We are migrating from elasticsearch to opensearch and could not migrate many queries as they are using runtimefields https://www.elastic.co/guide/en/elasticsearch/reference/current/sql-runtime-fields.html , also see related issues where work around using SQL does not work
#2320
What solution would you like?
allow users to specify scripted fields for SQL query when using API
What alternatives have you considered?
We tried using nested SQL query , but got various errors such as missing field, join related
Do you have any additional context?
https://www.elastic.co/guide/en/elasticsearch/reference/current/sql-runtime-fields.html
The text was updated successfully, but these errors were encountered: