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
Filter by lookup #4812
Comments
I am getting similar results for Druid data sources only I didn't realize it until I tried to look at the == results instead on !=. I'm on version v0.24.0. For some reason, the filter is not being applied correctly. I looked at the query that is generated and the lookup is passed and the filter is also applied in the query. This makes me think it is something on the druid end or how exactly the query is formed.
The former is slightly more performant. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue |
Dealing with the same issue when trying to filter with lookup, however the error i am getting is relevant to pydruid|:
|
Make sure these boxes are checked before submitting your issue - thank you!
Superset version
0.22.1
Expected results
When using a registered lookup as a dimension (using the dimensionSpec) we should be able to filter by it.
Actual results
When applying the filter we got no data as a result.
The text was updated successfully, but these errors were encountered: