Hi Team, I am trying to ingest metadata from MSSQL server. I am able to successfully customize base image "acryldata/datahub- ingestion:v0.8.40" and locally create a container and extract metadata through CLI. Question: I am having following in my terraform script to use the customized image from ECR which I pushed manually. datahub-ingestion-cron: enabled: true image: repository: ${customized_image} tag: ${image_version} I am unable to see a component “datahub-ingestion-cron” in my k8 workspace. Appreciate if you can help

Datahub-ingestion cron assumes an api where you specify the recipes you want + their schedules. See this file: https://github.com/acryldata/datahub-helm/blob/master/charts/datahub/subcharts/datahub-ingestion-cron/values.yaml

@incalculable-ocean-74010, thanks. Here is why I landed into using “dataHub-ingestion-cron”. I am using “v0.8.40” of images for all services and “v0.0.4” of acryldata/datahub-actions for datahub-actions. when tried ingestion for MSSQL source ran into “module pyodbc not found” error. Assumed customizing datahub-ingestion-cron by adding drives will resolve this issue.

Please update all services to 0.8.43, you should already be able to run managed ingestion directly from the UI so no need for ingestion-crons

Yes we are able to run ingestion from other sources like Glue, Athena, DBt etc. it's the MSSQL that had issues. Sure will update all services to 0.8.43 and share my findings.

cc @dazzling-judge-80093, just for your knowledge

@incalculable-ocean-74010, @dazzling-judge-80093, appreciate if you can take a look at this. Meanwhile I am trying to use datahub-ingestion-corn to deploy from job to ingest metadata through k8

Here it seems pyodbc module is missing. Please, can you run a

pip install pyodbc

and try again?

Where should I run pip install, I am trying to run this through UI

hi @little-breakfast-38102 just wanted to check in and see if you found a solution for this?

Yes I will tag you in the latest post where I shared dockerfile used for this.

Hi. Can you share your solution? After adding pip pyodbc and apt unixodbc-dev to actions image, ingestion venv still cannot find pyodbc (despite that in actions container import pyodbc works).