metabase.semantic_type not being synced for dbt 1.10 for new "meta" yml under "config"

[patygold]

After upgrading dbt-core to 1.10.8 and dbt-metabase library to 1.6.1, the sync of the "metabase.semantic_type" to Metabase stopped working.

If I write my column such as

    columns:
      - name: booking_id
        data_tests:
          - not_null
          - unique
        description: The id of the booking
        config:
          meta:
            metabase.semantic_type: type/PK

This doesn't work (The Semantic Type is empty)

Changing this to (old version of dbt)

    columns:
      - name: booking_id
        data_tests:
          - not_null
          - unique
        description: The id of the booking
        meta:
          metabase.semantic_type: type/PK

Then this worked as before, with the semantic type as "Entity Key"

I'm using the library in Python (v3.11.10), defining the the export as such

    dbt_metabase = DbtMetabase(
        manifest_path=MANIFEST_FILE,
        metabase_url=metabase.host,
        metabase_api_key=metabase.api_key,
        http_timeout=60,
    )

    schema_filter, model_filter = get_filters(config)

    try:
        dbt_metabase.export_models(
            metabase_database=config.metabase_database,
            skip_sources=True,
            sync_timeout=0,
            schema_filter=schema_filter,
            model_filter=model_filter,
        )
    except Exception as e:
        context.log.error(f"Errors in metadata sync: {e}")

No errors are being raised though, just the Semantic Type in Metabase is not being updated for all new columns.

[gouline]

So this works on the same Metabase version when used with dbt 1.9?

[patygold]

When I upgrade dbt-core to 1.10 (I skipped 1.9, actually, I had dbt-core==1.8.7 before), I've adjusted all of my .yml files to the new structure of the configuration (thus, with the "config" before the "meta").
I can't say it worked with 1.9, but I can say that, with the db-core==1.10 and the same Metabase version:

this works:

    columns:
      - name: booking_id
        data_tests:
          - not_null
          - unique
        description: The id of the booking
        meta:
          metabase.semantic_type: type/PK

this doesn't:

    columns:
      - name: booking_id
        data_tests:
          - not_null
          - unique
        description: The id of the booking
        config:
          meta:
            metabase.semantic_type: type/PK

No errors or anything. And I tested for the following semantic_types: PK, FK, Category, Quantity, CreationDate and CreationTimestamp. For all, the same the problem, I had to remove the "config" from my yml to work.

[gouline]

Sorry, I meant does it work on the same version of Metabase at all, to eliminate it as a factor. Thanks for providing all this information, I'll have a look.

[gouline]

I reproduced your issue using dbt-core 1.10.8, but it works with >=1.10.13 (latest is 1.10.15). Assuming there was a bug in dbt that didn't propagate meta values to the manifest (possibly related to dbt-labs/dbt-core#11992).