You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: this is technically possible with the newly added Cascade extractionsFn by using a javascript extractionFn, and the extraction filter like so: Cascade(lookup(some_lookup), javascript(d.match(/^lol/))) == "true" but that is cumbersome and while Plywood could be programmed to do it users using the Druid API directly will have a hard time working that one out.
Sugested solution
Every filter that takes a dimension should be able to also take an extraction function also. I.e. the filter dimension would become a DimensionSpec
It would be great to have the ability to express a filter on a dimension with and extractionFn.
Problem
It is currently not easy to express:
As a Druid filter. See this issues: implydata/pivot#119
Note: this is technically possible with the newly added Cascade extractionsFn by using a javascript extractionFn, and the extraction filter like so:
Cascade(lookup(some_lookup), javascript(d.match(/^lol/))) == "true"
but that is cumbersome and while Plywood could be programmed to do it users using the Druid API directly will have a hard time working that one out.Sugested solution
Every filter that takes a dimension should be able to also take an extraction function also. I.e. the filter
dimension
would become aDimensionSpec
So:
Would be equivalent to:
But would could also write:
This would apply to all filters.
Note that this change will make the extraction filter redundant as you could simply write:
The text was updated successfully, but these errors were encountered: