KeyError: 'details' for internal Metabase tables

[alex1bravo]

In the _exposures.py at a certain point you have the following code:

            table_names={
                t["id"]: ".".join(
                    [
                        dbname(t["db"]["details"]),
                        t["schema"] or DEFAULT_SCHEMA,
                        t["name"],
                    ]
                ).lower()
                for t in self.metabase.get_tables()
            },

It seems that recently the Metabase API, when you run self.metabase.get_tables(), returns also some internal tables. For example, this table here

{
  "description": null,
  "entity_type": "entity/GenericTable",
  "view_count": 0,
  "schema": "public",
  "database_require_filter": null,
  "db": {
    "uploads_schema_name": null,
    "description": "Internal Audit DB used to power metabase analytics.",
    "features": [
      "describe-fks",
      "index-info",
      "full-join",
      "window-functions/cumulative",
      "test/dynamic-dataset-loading",
      "describe-fields",
      "basic-aggregations",
      "temporal-extract",
      "identifiers-with-spaces",
      "actions/custom",
      "window-functions/offset",
      "now",
      "parameterized-sql",
      "convert-timezone",
      "nested-field-columns",
      "standard-deviation-aggregations",
      "test/jvm-timezone-setting",
      "date-arithmetics",
      "persist-models",
      "actions",
      "expression-aggregations",
      "percentile-aggregations",
      "connection-impersonation",
      "table-privileges",
      "right-join",
      "left-join",
      "native-parameters",
      "uuid-type",
      "schemas",
      "nested-queries",
      "describe-indexes",
      "expressions",
      "uploads",
      "set-timezone",
      "regex",
      "case-sensitivity-string-filter-options",
      "binning",
      "metadata/key-constraints",
      "datetime-diff",
      "upload-with-auto-pk",
      "inner-join",
      "advanced-math-expressions",
      "fingerprint",
      "native-parameter-card-reference"
    ],
    "uploads_table_prefix": null,
    "cache_field_values_schedule": "0 0 16 * * ? *",
    "timezone": null,
    "is_attached_dwh": false,
    "auto_run_queries": true,
    "metadata_sync_schedule": "0 27 * * * ? *",
    "name": "Internal Metabase Database",
    "settings": null,
    "caveats": null,
    "creator_id": 13371338,
    "is_full_sync": true,
    "updated_at": "2025-01-16T00:24:48.771475Z",
    "cache_ttl": null,
    "is_sample": false,
    "id": 13371337,
    "is_on_demand": false,
    "engine": "postgres",
    "initial_sync_status": "complete",
    "is_audit": true,
    "dbms_version": null,
    "uploads_enabled": false,
    "refingerprint": null,
    "created_at": "2024-01-18T00:12:05.675943Z",
    "points_of_interest": null
  },
  "show_in_getting_started": false,
  "name": "v_alerts",
  "caveats": null,
  "updated_at": "2025-01-16T00:24:48.771475Z",
  "active": true,
  "id": 274,
  "db_id": 13371337,
  "visibility_type": null,
  "field_order": "database",
  "is_upload": false,
  "initial_sync_status": "complete",
  "display_name": "V Alerts",
  "created_at": "2023-11-01T02:10:33.263249Z",
  "estimated_row_count": null,
  "points_of_interest": null
}

So, when you do t["db"]["details"], it breaks because it cannot find the details key.

IDK what a possible solution could be, but probably just ignore these Metabase internal tables. It could be done by filtering out the tables when the database name is Internal Metabase Database. IDK how reliable this solution is tho, or how likely is that Metabase will change the API behavior in the next future.

Let me know if I can help with this, thanks for the support!

[gouline]

I tracked it down to a Metabase pull request about auditing, which is an enterprise feature, so I can't reproduce it in the open source sandbox. Not sure how to best filter it, I just added a check for "details" 🤷‍♂