bryanck opened a new issue #10296:
URL: https://github.com/apache/incubator-superset/issues/10296
If you add a filter with an "in" clause to a word cloud chart in Superset
0.37rc1, it throws an error.
Request posted to /api/v1/chart/data:
{"datasource":{"id":21,"type":"table"},"force":false,"queries":[{"extras":{"where":""},"groupby":["app_name"],"is_timeseries":false,"metrics":[{"label":"hits"}],"order_desc":true,"orderby":[],"row_limit":100,"time_range":"Last
week","timeseries_limit":0,"timeseries_limit_metric":null,"filters":[{"col":"browser","op":"in","val":["Chrome","Safari"]}],"having":"","having_filters":[],"where":""}],"result_format":"json","result_type":"full"}
Response:
HTTP code 400
{"message":"Request is incorrect: {'queries': {0: {'filters': {0: {'op':
['Must be one of: ==, !=, >, <, >=, <=, LIKE, IS NULL, IS NOT NULL, IN, NOT IN,
REGEX.']}}}}}"}
This seems to be a problem with the /api/v1/chart/data endpoint. Charts that
post to /superset/explore_json don't have this issue.
#### How to reproduce the bug
Create a new word cloud chart. Add a filter with an "in" clause, e.g.
"Browser" in "Chrome","Safari".
Server sends back a 400 response code.
### Environment
(please complete the following information):
- superset version: 0.37 RC 1
- python version:3.6.11
- node.js version: 12.14.1
- npm version: 6.13.4
### Checklist
- [X] I have checked the superset logs for python stacktraces and included
it here as text if there are any.
- [X] I have reproduced the issue with at least the latest released version
of superset.
- [X] I have checked the issue tracker for the same issue and I haven't
found one similar.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
