Derived table bytes billed in Big Query

Hi!

I have a derived table in Looker querying over a partitioned table in Big Query. Due to the Big Query partitioning, the derived table query requires a date filter. Since users are querying over various time periods, I used the minimum date in the table.

When I go to an explore for the derived table, select a few columns and add a filter for the date - I see the ‘will process xxx bytes’ change with respect to the date filter I’m using.

Is the table scan then limited to the date filter set in Looker and not to the date set in the derived table query? The derived query date is being overridden by the Looker date, so Biq Query is only scanning the table for the filtered date in Looker.

I tried to find a billable bytes history in Big Query for Looker queries to verify what is being billed, but could not find a way.

Thanks

0 0 125