Guarding queries on a view from filtering on specific columns

[mstowe-digi]

Hello,

I have a view in Trino that joins a materialized view from an iceberg table for dimensions and a mysql table for facts.

Queries that are submitted to the view need to be anchored with 2 specific columns that the mysql table is indexed by to avoid full table scans. This is a large table with a lot of telemetry data that is indexed by a deviceId and timestamp.

materialized view:  deviceid, dimension1, dimension2, dimension3
(iceberg)

mysql table: deviceid, readingValue, readingTimestamp.
(index = (deviceid, readingTimestamp)

final view: deviceid, dimension1, dimension2, dimension2, readingValue, readingTimestamp.
(join on mview and mysql table)

When querying the final view we want to ensure that queries have a where clause that include deviceId at the very least so that the mysql table is not hit for a full table scan, and if that query parameter is missing error out/short-circuit the query, or something of that nature that protects the underlying database from really generic queries.

Can anyone advise on a strategy?

Thanks,
Matt