-
Notifications
You must be signed in to change notification settings - Fork 146
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] Dashboard filters issue with Quicksight #1900
Comments
@rupal-bq, is it a JDBC driver issue or Dashboards issue? |
Seems to be a JDBC driver issue. While applying filters, getting below error. |
I don't have access to Quicksight now. Can you reproduce that issue? Can you send me anonymized query please (SQL plugin prints it into logs)? What is the data mapping? |
SQL query:
mapping:
|
Thank you @rupal-bq! What versions of OpenSearch and JDBC driver is this using? |
Probably it is V2 parser issue: opensearchsql> select city as abc from bank group by city order by abc is not null, abc limit 100;
{'reason': 'Invalid SQL query', 'details': "can't resolve Symbol(namespace=FIELD_NAME, name=abc) in type env", 'type': 'SemanticCheckException'}
opensearchsql> select city as abc from bank group by city order by city is not null, abc limit 100;
fetched rows / total rows = 7/7
... I see alias is not supported in expression in @rupal-bq, please, confirm that the query is correct. I want to ensure that we found the right bug. |
Hi @Yury-Fridlyand, the query is correct. Didn't find much information in quicksight logs, it only had generic sql exception. |
Seems like this is related to: |
OpenSearch version is 2.5 but not sure what JDBC version (using Quicksight connector) |
Hi @rupal-bq , is there any progress on this? |
What is the bug?
While adding filters (as controls or otherwise), it gives an SQL exception/fails to populate any option in the dropdown, for both single-option and multi-option dropdown.
While selecting the filter as a raw text field, it accepts single as well multiple values, and works as expected.
The text was updated successfully, but these errors were encountered: