Heyho,\nI am unsure if the everywhere mentioned caching is really for query results?\nI have long-running queries ( 10minutes+) which are executed every time.\nThe config is definitely loaded, as I authenticate against LDAP which is set up in the config and working fine :)\nI tried different variations of the config (as the superset docs, snippets from Github issues + flask are kind of similar..bit a bit different sometimes ^^).\n\nMy current config for testing purposes includes\n```CACHE_DEFAULT_TIMEOUT = 60 * 60 * 24\nCACHE_CONFIG = {'CACHE_TYPE': 'filesystem', 'CACHE_DIR': '/tmp'}\nTABLE_NAMES_CACHE_CONFIG = {'CACHE_TYPE': 'filesystem', 'CACHE_DIR': '/tmp'}```\nBut during startup I still get the issue reported that I have no caching:\n```root@aw-superset:~# /opt/venvs/apache-superset/bin/superset run -p 8088 --with-threads --reload --debugger\nlogging was configured successfully\nINFO:superset.utils.logging_configurator:logging was configured successfully\n/opt/venvs/apache-superset/lib/python3.7/site-packages/flask_caching/__init__.py:192: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.\n  "Flask-Caching: CACHE_TYPE is set to null, "```\nDo I have something wrong in my cache settings?\nDo you have any working example for a filesystem cache? I wanted to get this running before I start spinning up a Redis :slightly_smiling_face: