title: Bigquery caching when hitting table would provide a different result?
body: <p>As part of our Bigquery solution we have a cron job which checks the latest table created in a dataset and will create more if this table is out of date.This check is done with the following query</p>
  
  <p><code>SELECT table_id FROM [dataset.__TABLES_SUMMARY__] WHERE table_id LIKE 'table_root%' ORDER BY creation_time DESC LIMIT 1</code></p>
  
  <p>Our integration tests have recently been throwing errors because this query is hitting Bigquery's internal cache even though running the query against the underlying table would provide a different result. This caching also occurs if I run this query in the web interface from Google cloud console. </p>
  
  <p>If I specify for the query not to cache using the </p>
  
  <pre><code>queryRequest.setUseQueryCache(false)
  </code></pre>
  
  <p>flag in the code then the tests pass correctly.</p>
  
  <p>My understanding was that Bigquery automatic caching would not occur if running the query against the underlying table would provide a different result. Am I incorrect in this assumption in which case when does it occur or is this a bug?</p>