Hi, I used the upload data feature for the first time yesterday. I successfully uploaded my CSV and could use it in a question and visualisation successfully. Now, today, Ive logged back in and it gives me an error that the CSV isnt found? But I see the model in my collection and it remembers the field names?
What did you configure as the upload destination? And what version of Metabase are you running?
If you used the Sample Database then it might have gotten splatted over in a Metabase upgrade, or a H2 hiccup, or reset by a container replacement. A permanent location outside the Metabase container is recommended.
Thanks @dwhitemv for the reply.
We are using version v0.47.10 (free version)
Not sure what “configure” means for upload in your question, but I simply “uploaded data” (cloud icon) to a collection, then it shows up as a model in the collection.
In terms of your comments about upgrade, H2 hiccup and container replacements - are these questions for my devops team? or uncontrollable things managed by Metabase themselves? (excuse my noob questions)
0.47 is very old. It looks like that version was the first with CSV uploads. From the announcement, it sounds like it works like it does in 0.55 where the admin must set a database for CSVs to be written to. That database must be running MySQL or PostgreSQL.
Best I can suggest is to contact your Metabase administrator (your DevOps team, if they’re responsible for it) and ask them if they remove CSV uploads automatically, or if there is a problem with the uploads.
Metabase itself would never remove a CSV upload (in fact, in the OSS versions, while you can delete the model, the database table remains; it has to be cleaned up manually).
As far as other exceptional events – upgrades and container replacements would be done by your Metabase administrator. H2 is an in-server storage system with reliability problems (thus “hiccups”); the Sample Database uses it, and you can temporarily use it as the Metabase application database, but if you value your data you don’t want to use it for a permanent installation as the day will come that H2 will crash and eat it. I doubt that’s a problem for your install.
If you selected the H2 database which is the Sample Database as your destination. There is a big yellow warning that says that this DB is for testing only and files may disappear. Since it’s a file storage, every restart will force the file to be cleaned.
Also please upgrade to 1.55.11 which is the latest cause no one is going to go that back to test this out. You will get more help if you upgrade + much more features and bug fixes