MariaDB 10.11.7 is classified as too old (RocksDB)

[Charlie-MPC]

Describe the bug A connection is established, I can select 1 from dual, but all queries against tables fail, no tables are shown.

Logs

---

WARNING: Metabase only officially supports MySQL 5.7/MariaDB 10.2 and above. All Metabase features may not work properly when using an unsupported version.

---

"MyRocks supports only READ COMMITTED and REPEATABLE READ isolation levels. Please change from current isolation level READ-UNCOMMITTED",

To Reproduce Install Ubuntu 24.04, apt update; apt install mariadb; ( Server version: 10.11.7-MariaDB-2ubuntu2 Ubuntu 24.04 ) I'm using SSL to connect. JDBC options I've used:

disableSslHostnameVerification=true

disableSslHostnameVerification=true&trustServerCertificate=true

disableSslHostnameVerification=true&trustServerCertificate=true&sessionVariables=tx_isolation='READ-COMMITTED'

I've set MariaDB to run globally with READ-COMMITTED and also tried REPEATABLE-READ

Expected behavior Tables should show on the Browse page for the DB. Queries should run against tables.

Severity I'm trying to use Rocks for analytics purposes. The data isn't getting any smaller. I suppose I could try to start over on an older OS release.

Additional context I think the message about isolation level is a red herring. It looks more like this MariaDB version is unrecognized and classified as too old, when it's probably too new.

Metabase Diagnostic Info

{
  "browser-info": {
    "language": "en-US",
    "platform": "MacIntel",
    "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:126.0) Gecko/20100101 Firefox/126.0",
    "vendor": ""
  },
  "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": [
      "mysql",
      "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
    }
  }
}

[Charlie-MPC]

After adding an InnoDB table to the DB as a test, it has become visible in Metabase. So the RocksDB tables are ignored. Is that intentional?

[SBK79]

tables that use Rocksdb engine are not visible for me, is this issue fixed ? is there a way to see rocksdb tables on metabase for now ?

[dragonsahead]

There’s not. We don’t support rocks db

[SBK79]

There’s not. We don’t support rocks db

will you support it in near future?

[dragonsahead]

It depends on how many people ask for it, currently only 2 people did

[dragonsahead]

if someone can test 50.7 or 50.8, we now use read commited @Charlie-MPC @SBK79

[SBK79]

@paoliniluis I tested metabase version 50.8 and unfortunately it didn't find rocksdb tables again

[perivamsi]

This is not a bug and should not be a P1 since we don't support rocksdb.