AND
).
Filtering is pushed down - every filter is pushed down to apply as early as possible, resulting in higher performance.
orders
after joining customers
.In some cases, it is better to separate filters by entity and combine them only in a dynamic dataset or a SQL query.
If using two attributes as:customers
before joining it to orders
, resulting in a better performance.customers.custkey
and apply this filter of shipped orders:
orders
filters customers
after the JOIN between them.
Whether a filter on an entity applies to a different entity depends on the relationship.
See cross filtering for more details.