OskarSorensen opened a new issue, #24171:
URL: https://github.com/apache/superset/issues/24171
#### How to reproduce the bug
With GLOBAL_ASYNC_QUERIES enabled view an embedded dashboard with the
`superset-ui/embedded-sdk` NPM package using a guest token. When Superset has
finished processing the queries and notifies the frontend to go fetch the
specific cache key (`api/v1/chart/data/{cache_key}`) a fatal error and a HTTP
422 Unprocessable Entity is returned instead. After some experimentation I've
found out that this only happens if a RLS clause has been added to the quest
token. It seems like the presence of an RLS clause causes this - even if the
clause is simply `1 = 1`. If a guest token without RLS is used then it works as
expected.
### Expected results
That the request with the guest token containing an RLS clause can
successfully fetch data from `api/v1/chart/data/{cache_key}`
### Actual results
Fatal error and HTTP 422 Unprocessable Entity
### Environment
- browser type and version: `Chrome 113.0.5672.127`
- superset version: `2.1.0`
- python version: (docker)
- node.js version: (docker)
- any feature flags active: `ENABLE_TEMPLATE_PROCESSING, DASHBOARD_RBAC,
DASHBOARD_CROSS_FILTERS, EMBEDDED_SUPERSET, DRILL_TO_DETAIL,
DASHBOARD_NATIVE_FILTERS, HORIZONTAL_FILTER_BAR, GLOBAL_ASYNC_QUERIES,
GLOBAL_ASYNC_QUERIES_TRANSPORT = "polling"`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
