Hi, I'm trying to evaluate datahub for my company and we've been stuck for a couple weeks now. I could use any advice at this point - all suggestions welcome. Overview: Attempting to run an MSSQL source ingestion through the UI Config: Token based auth is disabled for evaluation. Recipe: IP/Port are faked here

source:
    type: mssql
    config:
        password: '${secretPass}'
        database: DatabaseName2
        host_port: '192.168.1.1:9999'
        username: '${secretUser}'

The sink configuration is no problem. I've tinkered with it extensively and it was working fine for us to ingest data at one point. Unfortunately we tried to compose DataHub again and lost this functionality on the current image. When running UI ingestion, this is the relevant error I see:

'[2022-12-28 19:53:58,671] ERROR    {datahub.ingestion.run.pipeline:127} - mssql is disabled; try running: pip install '"'acryl-datahub[mssql]'\n"

We have installed the plugin as requested by the error message and also followed the steps to set up the ODBC driver, as well as pyodbc just in case that is an issue. I have attached three files here: 1. The Error Log 2. Output of

datahub check plugins --verbose

3. Config showing ODBC driver installed Any idea what I'm doing wrong, or advice on how to further diagnose the issue?

Are you running on k8s? Where did you run

pip install

?

Sorry I had to reach out to get some more info on the install. We are hosting it through I think Amazon EKS, following the setup guide for kubernetes in the documentation.

If you want to run through ingestion UI, you need to run pip install on the acryl-action pod.

@rhythmic-lock-29204 is this issue still affecting you?

@astonishing-answer-96712 Oh gosh, thanks for checking in. I'm here at the moment working with my team now that they're all back from holiday to resolve our setup issues. We're running PostgreSQL and Snowflake ingestion tests right now. The Snowflake is failing as well, but I can't make heads or tails of the error message it produces. I should know if MSSQL is working shortly - we were running the pip install command on the server instead of the acryl-actions pod so I think that's why that specific ingestion failed.

@big-carpet-38439 any thoughts here?

@rhythmic-lock-29204 so it looks like you have all the required packaged but the pod was killed half way. I suspect it didn't have enough resource i.e memory or there was autoscaling policy that might kill it half way.