-
Notifications
You must be signed in to change notification settings - Fork 139
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
[BUG] unsupported operator: if when using sql API #2320
Comments
I found the issue since I want to group by data and also transform before group by , I need to move group by in outer nested query. I will test and reopen issue if I get same error |
I found multiple issues and created feature request to add support for scripted field #2325 . any guidance is appreciated.
|
looks like if I remove fetch_size parameter I get the results, but no cursor is present
if fetch_size is the issue , I wonder if I can paginate using OFFSET,LIMIT at the end of the query? |
adding @Yury-Fridlyand for help as I see there PR created for pagination related changes #1752 Yuri do you know what is limitation of V1 LIMIT OFFSET,PAGE_SIZE approach for pagination? background: we are migrating from ES 7.17 to Opensearch 2.8.0+ and facing issues with some of the queries which use pagination and runtime fields. |
The failed query in #2320 (comment) has 2 problems.
|
What is the bug?
Opensearch version 2.8.0
we are migrating from elasticsearch to opensearch and planning to use nested sql queries to replace runtime field which were supported in elasticsearch sql API
after following documentation from https://opensearch.org/docs/2.0/search-plugins/sql/sql-ppl-api/#query-api
when I try to run sql query using if operator I get following exception
{
"error": {
"reason": "There was internal problem at backend",
"details": "unsupported operator: if",
"type": "UnsupportedOperationException"
},
"status": 503
}
same query works in query workbench. if I use nested query only group by fields are returned.
How can one reproduce the bug?
Steps to reproduce the behavior:
steps to replicate in dev console (queries works workbench)
What is the expected behavior?
output from query workbench and SQL needs to be consistent
What is your host/environment?
Do you have any screenshots?
N/A
Do you have any additional context?
N/A
The text was updated successfully, but these errors were encountered: