What Happened
The acryl-datahub python package has an unpinned dependency on the open source ruamel-yaml project (meaning our package isn't tied to one known/tested version of ruamel, and is subject to automatic upgrades of that library).
On December 31st, 2025, the ruamel-yaml library released version 0.19.0 with breaking changes that require C compilation tools during installation. This new version is incompatible with DataHub's execution environment and caused ingestion failures under various circumstances. DataHub has fixed all accessible ingestion connectors. Action will be required if you are utilizing connectors that DataHub does not have access to change.
Who Is Affected
Most ingestion connectors were affected (See the Appendix below for the list of affected connectors).
(FIXED) For all ingestion connectors running via Managed Ingestion in a hosted DataHub Cloud instance, DataHub has already applied a fix. Subsequent ingestion runs will succeed.
For any ingestion running via CLI (command-line interface) on a customer machine, or any ingestion running via Managed Ingestion in a DataHub instance deployed within a customer's network, customers will need to apply the fixes described below themselves.
For customers on a DataHub server version earlier than v0.3.15, all new ingestion recipes will fail unless they are using CLI version 1.3.1.5. -> You will need to upgrade to this new CLI version.
DataHub Cloud: Remediation for UI Ingestion Managed Recipes
(FIXED) Nothing needs to be done for Ingestion recipes created via Managed Ingestion before Jan 1st, 2025. All have already been updated to have the Extra Pip Libraries set to include `[“ruamel-yaml<0.19”]` under Advanced on the final page of ingestion configuration:
On January 2nd, 2026, we will apply a change to all Server versions on 0.3.15.X to set the default CLI version to 1.3.1.5. However, new recipes on DataHub server versions under 0.3.15 will not have this applied. When creating a new recipe via Managed Ingestion on server versions under 0.3.15, either set the extra pip libraries to the fix, or set the cli version to 1.3.1.5. DataHub will also be scanning for these recipes and automatically applying the remediation of the Extra Pip Library setting.
Remediation for Customer-Managed Ingestion Recipes (CLI fix)
We've released DataHub CLI version 1.3.1.5 with the fix. Upgrading will address the issue:
#!/bin/bash
python3 -m pip install acryl-datahub==1.3.1.5
If you're using connector plugins, reinstall them as well:
#!/bin/bash
pip install 'acryl-datahub[mysql]==1.3.1.5'Replace mysql above with your specific connector(s) as needed.
Alternative: Temporary Workaround
If you cannot upgrade immediately, you can temporarily pin ruamel-yaml to a compatible version:
#!/bin/bash
python3 -m pip install --upgrade --force-reinstall acryl-datahub 'ruamel-yaml<0.19'Verification
After upgrading or applying the workaround, verify your installation:
#!/bin/bash
python3 -m datahub version
datahub ingest -c <path/to/your-recipe.yml>Remediation for Customer-Managed (on-premise) DataHub Instances
Set the helm value `global.datahub.managed_ingestion.defaultCliVersion` to `1.3.1.5`. For all existing recipes, there are two options:
- Upgrade them to `1.3.1.5`
- Set the Extra Pip Libraries to include `[“ruamel-yaml<0.19”]` under Advanced on the final page of ingestion configuration:
Timeline of DataHub Remediation for Managed Ingestion in DataHub Cloud Instances
On Jan 1 2026, at 5:28pm PST, DataHub pinned the version of ruamel-yaml for all customer recipes being run via Managed Ingestion. This was in order to fix the issue as soon as possible. For all ingestion recipes run via managed ingestion, on their next run, they will succeed. Some recipes are already succeeding. All recipes that are not configured via DataHub UI in a DataHub Cloud instance will continue to fail.
Questions or Issues?
If you continue to experience problems after upgrading, please:
- Contact DataHub Support via our Customer Portal.
- Join our Slack community for real-time help
We apologize for the inconvenience and are implementing stricter dependency pinning across all our packages to prevent similar issues in the future.
Appendix - Affected Connectors
Ingestion connectors that were affected by the unpinned ruamel-yaml issue:
- abs - Azure Blob Storage
- airflow - Airflow integration
- azure-ad - Azure Active Directory
- bigquery-slim - BigQuery without SQL profiling
- cassandra - Apache Cassandra
- circuit-breaker - Circuit breaker pattern
- datahub-business-glossary - Business glossary files
- datahub-debug - Debug utilities
- datahub-lineage-file - Lineage file ingestion
- dataplex - Google Dataplex
- dbt - dbt integration
- dbt-cloud - dbt Cloud
- delta-lake - Delta Lake
- dynamodb - AWS DynamoDB
- elasticsearch - Elasticsearch
- excel - Excel files
- feast - Feast feature store
- fivetran - Fivetran integration
- gcs - Google Cloud Storage
- glue - AWS Glue
- grafana - Grafana
- great-expectations - Great Expectations plugin
- iceberg - Apache Iceberg
- iceberg-catalog - Iceberg catalog
- json-schema - JSON Schema
- kafka - Apache Kafka
- ldap - LDAP
- looker - Looker
- lookml - LookML
- metabase - Metabase
- mlflow - MLflow
- mode - Mode Analytics
- mongodb - MongoDB
- neo4j - Neo4j
- nifi - Apache NiFi
- okta - Okta
- powerbi - Power BI
- powerbi-report-server - Power BI Report Server
- preset - Preset (Superset cloud)
- pulsar - Apache Pulsar
- qlik-sense - Qlik Sense
- redash - Redash
- s3 - AWS S3 (with profiling)
- s3-slim - AWS S3 (without profiling)
- sac - SAP Analytics Cloud
- sagemaker - AWS SageMaker
- salesforce - Salesforce
- sigma - Sigma Computing
- slack - Slack integration
- snaplogic - SnapLogic
- snowflake-slim - Snowflake without SQL profiling
- sql-parser - SQL parser utility
- sql-queries - SQL queries from logs
- superset - Apache Superset
- tableau - Tableau
- vertexai - Google Vertex AI