Incorrect browser caching of query results

[ari-e]

Issue Summary

During local development with Redash, the browser incorrectly caches results from previous Redash deployments.

After building, tearing down, and re-building my dev deployment a few times I noticed that new queries were returning the result of previous queries from several docker-compose up's ago. For example, I would have some group by query and then after several tear-downs and re-builds of the service I would run a simple count() and the result would be the same as that group by from an hour ago. What’s even weirder is running this count() many times in a row would lead to different results. Sometimes it would be the correct answer, sometimes it would return that aggregate result, and sometimes it would return a result from another query I had run previously.

I finally realized that disabling caching on my browser stopped this issue. The changes I made are simple changes to the internals of a data source and should have no effect on anything related to this type of behavior.

See https://discuss.redash.io/t/maddening-browser-cache-behavior-in-dev-environment/4342 for more.

Steps to Reproduce

1. Follow https://redash.io/help/open-source/dev-guide/docker to set up a local Redash dev deployment
2. Bring up the services, connect a data source, run some queries
3. Tear down the services
4. Repeat 2 and 3 a few times
5. Open localhost:5000 and enter a query in the query editor. Press "Execute" many times in a row to see different results.

Technical details:

• Redash Version: Built from master which was e5e926b at the time of testing
• Browser/OS: Chrome 76.0.3809.100
• How did you install Redash: Based off https://redash.io/help/open-source/dev-guide/docker I created a new docker-compose file https://github.com/rockset/community/blob/master/redash/docker-compose.yml for one step setup