Metabase is deleting the information uploaded by csv

[ingluisandres]

Describe the bug
2 days ago I uploaded several csv files and generated 3 different tables in my manuable-cross-table database

• zips
• labels
• tracking_info

but today the information disappeared, and the same thing happened to me before

Logs

[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:00-06:00 INFO metabase.sync.util STARTING: Sync metadata for postgres Database 166 ''manuable-cross-table''
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util STARTING: step ''sync-dbms-version'' for postgres Database 166 ''manuable-cross-table''
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util FINISHED: step ''sync-dbms-version'' for postgres Database 166 ''manuable-cross-table'' (178,7 ms)
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util STARTING: step ''sync-timezone'' for postgres Database 166 ''manuable-cross-table''
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util FINISHED: step ''sync-timezone'' for postgres Database 166 ''manuable-cross-table'' (236,6 ms)
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util STARTING: step ''sync-tables'' for postgres Database 166 ''manuable-cross-table''
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.sync-metadata.sync-timezone :postgres database 166 default timezone is "GMT"
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util FINISHED: step ''sync-tables'' for postgres Database 166 ''manuable-cross-table'' (3,3 ms)
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util STARTING: step ''sync-fields'' for postgres Database 166 ''manuable-cross-table''
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util FINISHED: step ''sync-fields'' for postgres Database 166 ''manuable-cross-table'' (1,2 ms)
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util STARTING: step ''sync-fks'' for postgres Database 166 ''manuable-cross-table''
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util FINISHED: step ''sync-fks'' for postgres Database 166 ''manuable-cross-table'' (3,9 ms)
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util STARTING: step ''sync-indexes'' for postgres Database 166 ''manuable-cross-table''
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util FINISHED: step ''sync-indexes'' for postgres Database 166 ''manuable-cross-table'' (1,9 ms)
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util FINISHED: step ''sync-metabase-metadata'' for postgres Database 166 ''manuable-cross-table'' (37,0 µs)
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util STARTING: step ''sync-metabase-metadata'' for postgres Database 166 ''manuable-cross-table''
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util STARTING: step ''sync-table-privileges'' for postgres Database 166 ''manuable-cross-table''
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util FINISHED: step ''sync-table-privileges'' for postgres Database 166 ''manuable-cross-table'' (123,8 ms)
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util FINISHED: Sync metadata for postgres Database 166 ''manuable-cross-table'' (958,1 ms)
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util STARTING: Analyze data for postgres Database 166 ''manuable-cross-table''
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util STARTING: step ''fingerprint-fields'' for postgres Database 166 ''manuable-cross-table''
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util FINISHED: step ''classify-fields'' for postgres Database 166 ''manuable-cross-table'' (27,3 µs)
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util FINISHED: step ''classify-tables'' for postgres Database 166 ''manuable-cross-table'' (30,5 µs)
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util FINISHED: step ''fingerprint-fields'' for postgres Database 166 ''manuable-cross-table'' (1,9 ms)
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util STARTING: step ''classify-fields'' for postgres Database 166 ''manuable-cross-table''
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util STARTING: step ''classify-tables'' for postgres Database 166 ''manuable-cross-table''
[26e84b0b-4caa-436c-a8ce-017136b1bc4f] 2024-05-10T08:04:01-06:00 INFO metabase.sync.util FINISHED: Analyze data for postgres Database 166 ''manuable-cross-table'' (21,1 ms)

To Reproduce
Steps to reproduce the behavior:

1. have csv uploads enabled
2. upload a csv correctly
3. wait 2 days

Expected behavior
You should no longer have any tables in your database.

Severity
How severe an issue is this bug to you? Is this annoying, blocking some users, blocking an upgrade or blocking your usage of Metabase entirely?
We are about to begin a process to analyze external information that is not in our databases, to audit whether our margins are correct in real time. It would be very useful for me if you could support me as soon as possible.

Additional context
A new database was created on Amazon, only for csv uploads in metabase. This was the selected instance db.t3.micro

Metabase Diagnostic Info

{
  "browser-info": {
    "language": "en-US",
    "platform": "Linux x86_64",
    "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36",
    "vendor": "Google Inc."
  },
  "system-info": {
    "file.encoding": "UTF-8",
    "java.runtime.name": "OpenJDK Runtime Environment",
    "java.runtime.version": "11.0.23+9",
    "java.vendor": "Eclipse Adoptium",
    "java.vendor.url": "https://adoptium.net/",
    "java.version": "11.0.23",
    "java.vm.name": "OpenJDK 64-Bit Server VM",
    "java.vm.version": "11.0.23+9",
    "os.name": "Linux",
    "os.version": "5.10.215-203.850.amzn2.x86_64",
    "user.language": "en",
    "user.timezone": "GMT"
  },
  "metabase-info": {
    "databases": [
      "postgres"
    ],
    "hosting-env": "unknown",
    "application-database": "postgres",
    "application-database-details": {
      "database": {
        "name": "PostgreSQL",
        "version": "14.10"
      },
      "jdbc-driver": {
        "name": "PostgreSQL JDBC Driver",
        "version": "42.7.2"
      }
    },
    "run-mode": "prod",
    "version": {
      "date": "2024-05-02",
      "tag": "v1.49.8",
      "hash": "38cb850"
    },
    "settings": {
      "report-timezone": null
    }
  }
}

[paoliniluis]

Hi, Metabase does not issue a drop table, can you search for those tables with a database gui?

[darksciencebase]

@ingluisandres was it by any chance the Sample Database that was set as the destination for uploads?

[calherries]

This isn't the sample database, based on the diagnostic info this is a postgres DB.

Something else must be causing the tables to be dropped from the database other than Metabase. The only DROP TABLE calls in Metabase 49.8 are used on persisted model tables, or to clean up new upload tables immediately after a failed upload. I'm removing the P1 and closing the issue for this reason.