cccs-RyanK commented on PR #22168:
URL: https://github.com/apache/superset/pull/22168#issuecomment-1516705497

   
   
   
   > > How will this filter behave considering inter filter features such as 
Values depend on other filters and Filter scopes? Specially in the case where 
we have a SQL value and it's hard to determine the referenced column/dataset.
   > 
   > @cccs-RyanK Just to be more clear about the above point. There's a feature 
called **Values depend on other filters** (check 
[this](https://github.com/apache/superset/pull/23566) PR's video) which allows 
you to establish an hierarchy between filters. One example is when you have a 
State and City filters and you want to change the City's values depending on 
the selected value in State. This all works because there's a clear definition 
of the dataset and column when creating a filter. When you introduce a SQL 
filter, we don't know what's the column (or even if the SQL returns a column), 
so I'm wondering how all the features that depend on this definition will work. 
I think we need to at least disable these features when working with a SQL 
filter. If I defined the State filter as a SQL filter, then it shouldn't appear 
as one of the options in **Values depend on other filters** when configuring 
the City filter.
   
   @michael-s-molina thank you for the clarification! Yes I think that feature 
will need to be disabled on the SQL filter based on the reasons you mentioned. 
As for scoping, the SQL filter should work the same as other filters such as 
Time column filter which only specifies the dataset and not a specific column. 
   
   Lastly, I also agree about the horizontal filter bar I will test and adjust 
the popover so that it pops below instead of to the right in that case. Aiming 
to work on this soon.


-- 
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]

Reply via email to