-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
How to add greater than filter in apache superset? #9974
Comments
Issue Label Bot is not confident enough to auto-label this issue. See dashboard for more details. |
@sedhha Agree, this would be great if dynamic filters added to Superset. I am not sure if it works for your problem, but you can try to apply CASE function to the range you need to filter. In order to do this, just add a new column in datasource editor with required SQL, then use this column in FIlter View.
|
Oh amaing @aussat Thanks a lot will try this out. |
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 |
Any update how we can add less than greater than filter in Filter Box so we can apply it on the dashboard, we do get to add these filters in other charts, but not in Filter Box |
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 |
@junlincc |
Although we can filter columns by range in explore chart screen, it is weird that we cannot filter columns by range in dashboard filters. Any progress? |
Hi all |
@aonurdemir @vialcollet the new native filters feature is currently under heavy development, and we've already implemented a range filter which adds this feature (greater than, less than and range). Expect the feature to be in testable state fairly soon, but general availability is probably still a few months away. |
while you are waiting for the new features, you could try using jinja template to create range filter as workaround. |
Hello, |
Is there any update for this in superset 2.0 ? |
@erfanu25 please take a look at the Numerical Range Filter in Dashboard Native Filters which has been available for quite some time. |
Has superset changed its folder locations and interface? From a youtube tutorial, I found these options available in filter box:
![image](https://user-images.githubusercontent.com/36355685/83600250-c86f5c80-a58b-11ea-8e90-22c9de9ae1b8.png)
![image](https://user-images.githubusercontent.com/36355685/83600336-fb195500-a58b-11ea-853a-003ac6f48a7a.png)
But what my filter looks like is:
I want to apply a filter box which gives me flexibility to apply a filter over ranges. For example, this is my table:
![image](https://user-images.githubusercontent.com/36355685/83600423-3025a780-a58c-11ea-8354-a2eaa583ccf1.png)
I want to add a filter where it should display only those table results where videos>=100 and videos<=10000. Although filter allows me to select multiple value but what it doesn't allow me is to apply ranges, and as you know there are so many values between these two ranges, it gets very inefficient to apply these filters.
I tried to apply the filter as shown below:
![image](https://user-images.githubusercontent.com/36355685/83601395-2735d580-a58e-11ea-8eac-3d71ee20228e.png)
![image](https://user-images.githubusercontent.com/36355685/83601435-37e64b80-a58e-11ea-80b5-5305fc83288f.png)
![image](https://user-images.githubusercontent.com/36355685/83601480-50566600-a58e-11ea-93fa-69c4187580ba.png)
![image](https://user-images.githubusercontent.com/36355685/83601525-63693600-a58e-11ea-9a83-28d7caa0b52a.png)
![image](https://user-images.githubusercontent.com/36355685/83601599-84318b80-a58e-11ea-826a-5da1a5f9ecd7.png)
But how it works is this way:
When we look at time filter:
It works well and offers tons of customization, I was just curious if we can dynamically filter time then why not other values. Please do let me know if you have something for this.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: