Affects Version/s: None
Fix Version/s: 4.0.0
If Hive is configured with an authorization hook like Sentry, and a view is created with a WHERE clause referencing a different view' user has no access to, user cannot access the view as view' is considered direct input.
If test_user has read permission for only db3 (but not db1 or db2), their query
will fail with :
WHERE IN and WHERE EXISTS cause the same issue.
Cascading views created with no WHERE clauses (i.e. with simple SELECTs and FROM clauses) work fine.