cberge908 opened a new issue, #30844: URL: https://github.com/apache/superset/issues/30844
### Bug description We have a SQLite DB with a flat table, which we are using inside one of our dashboards. This SQLite DB is getting synchronized to an Azure Blob from the original source every hour. To make it available to Superset, we have mounted this Blob into the Superset container on our AKS cluster using [Blobfuse2](https://learn.microsoft.com/en-us/azure/aks/azure-csi-blob-storage-provision?tabs=mount-blobfuse%2Csecret#use-the-persistent-volume). After setting `PREVENT_UNSAFE_DB_CONNECTIONS = False` in the Superset config we were able to connect to the mounted SQLite file. Creating dashboards with the data coming from this file works perfectly fine. A few days later we have recognized that the data was not getting updated (as the underlying DB file in the Blob is getting updated every hour with the latest data). The file on the Blob had a recent timestamp, but the DB file mounted into the container had a timestamp from a few days ago. After restarting the Superset deployment the DB file inside the container had a recent timestamp and the fresh data was visible in our Dashboards + SQL Lab. I have a feeling that the file is being locked by Superset after opening the first Dashboard using it (or SQL Lab). In summary: 1. Sync SQLite DB with data to Azure Blob 2. Mount Azure Blob to Superset instance via Blobfuse2 3. Set `PREVENT_UNSAFE_DB_CONNECTIONS = False` in Superset config 4. Restart Superset 5. Connect to SQLite DB on mounted Blob in filesystem 6. Create a dashboard/ use the connected DB in SQL Lab 7. Update DB file on Blob 8. DB file is not getting updated/ showing latest data in superset ### Screenshots/recordings File inside container before restart  File inside Blob container  File inside container after restart  (Note: Local time of my machine is UTC +1, server time is UTC - therefore the slight derivation) ### Superset version 4.0.2 ### Python version 3.10 ### Node version I don't know ### Browser Chrome ### Additional context _No response_ ### Checklist - [X] I have searched Superset docs and Slack and didn't find a solution to my problem. - [X] I have searched the GitHub issue tracker and didn't find a similar bug report. - [X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
