You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@superset.apache.org by GitBox <gi...@apache.org> on 2017/10/18 19:35:29 UTC

[GitHub] Mogball opened a new issue #3689: [Filters] Bugs with Druid filters and filter UI

Mogball opened a new issue #3689: [Filters] Bugs with Druid filters and filter UI
URL: https://github.com/apache/incubator-superset/issues/3689
 
 
   Make sure these boxes are checked before submitting your issue - thank you!
   
   - [x] I have checked the superset logs for python stacktraces and included it here as text if 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
   
   
   ### Superset version
   0.20.4
   
   There are a bunch of weird bugs with filters for Druid datasources, due to the method `get_filters` in `superset/connectors/druid/models` incorrectly handling edge cases.
   
   - An empty `in` or `not in` filter that <strong>comes after</strong> a populated filter causes `'NoneType' has no attribute 'filter'`
   - Adding a `==` or `!=` filter with the default null value will be properly interpreted as `not null` or `is null` but then adding a value and removing it (with the 'x' or by selecting a null value in the dropdown) will cause `object of type 'NoneType' has no len()`
   - `>=` and `>` do not seem to work while `<=` and `<`  give `'bool' has no attribute 'filter'`
   - All four of the above give the `'bool' has no attribute 'filter'` when they are preceded by a valid filter
   
   UI Bugs,
   
   - Selecting a null value in the dropdown for one of the string type filters and then switching the operator gives `prop 'value' should not be null...`
   - Typing a value then gives `Filter is changing an uncontrolled input of type text to be controlled`
   
   Just can't away from these filters :/
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services