Investigating Error When Ingesting Metabase in Datahub

all-things-deployment
1

Original Slack Thread

Hello Team, i’m trying to ingest Metabase in Datahub.
We’re using Metabase 0.47.1 and Datahub 0.10.4 and I’m using this config

  type: "metabase"
  config:
    connect_uri: my-uri
    username: "my-user"
    password: "my-password"
    default_schema: public
    env: DEV


sink:
  type: "datahub-rest"
  config:
    server: "myserver"
    token: "my-token"
    max_threads: 1```
I’m getting this error:
```ConfigurationWarning: env is deprecated and will be removed in a future release. Please use platform_instance instead.
  config = MetabaseConfig.parse_obj(config_dict)
[2023-09-13 11:09:19,513] ERROR    {datahub.entrypoints:199} - Command failed: Failed to configure the source (metabase): Expecting value: line 1 column 1 (char 0)```
I would like to know if I’m doing something wrong ? or if Metabase is not compatible with this version
Thanks for your help
2

Hi - this is strange, the recipe seems fine but not really sure why it’s throwing decoding error. <@UV5UEC3LN> any ideas?

3

I’m not sure, this is more <@UV14447EU>’s forte

4

<@U05P2S5DNR5> is this all the log?

5

Hello <@UV14447EU>, yes that’s all the logs I get. I don’t know if it’s the reason, but we host Metabase on premise and we setup Cloudflare Access on it, but when I saw the https://github.com/datahub-project/datahub/blob/ee7930b465f64ea1af2b7876859cc37bdce7aecb/metadata-ingestion/src/datahub/ingestion/source/metabase.py#L149|header passed to the Metabase connexion, it does not support CF-Access-Client-Id and CF-Access-Client-Secret . Can this be the problem ?