Skip to content

postgres & redshift ddl and e2e fixes #26367

Merged
SumanMaharana merged 2 commits intomainfrom
postgres-fixes
Mar 10, 2026
Merged

postgres & redshift ddl and e2e fixes #26367
SumanMaharana merged 2 commits intomainfrom
postgres-fixes

Conversation

@SumanMaharana
Copy link
Copy Markdown
Contributor

@SumanMaharana SumanMaharana commented Mar 10, 2026

Describe your changes:

This pull request improves Redshift database ingestion robustness and compatibility by handling Redshift-specific SQLAlchemy issues and updating test utilities. The most significant changes include overriding problematic Redshift dialect methods to prevent transaction failures, ensuring aborted transactions are rolled back to keep connections usable, and modernizing test code to use newer SQLAlchemy APIs.

Redshift dialect compatibility and error handling:

  • Added a custom get_temp_table_names method to the Redshift dialect to avoid querying pg_catalog.pg_class.relpersistence, which does not exist in Redshift and would otherwise cause transaction-aborting errors. The method simply returns an empty list. (get_temp_table_names, metadata.py, utils.py) [1] [2] [3]
  • Updated exception handling in get_all_table_ddls to explicitly roll back the connection if a ProgrammingError occurs, preventing the connection from remaining in a failed transaction state and ensuring subsequent queries can succeed. (sqlalchemy_utils.py) [1] [2]

Testing and code modernization:

  • Updated test mixins to use exec_driver_sql instead of execute(text(...)), aligning with modern SQLAlchemy best practices and improving compatibility. (common_e2e_sqa_mixins.py)

Type of change:

  • Bug fix
  • Improvement
  • New feature
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation

Checklist:

  • I have read the CONTRIBUTING document.
  • My PR title is Fixes <issue-number>: <short explanation>
  • I have commented on my code, particularly in hard-to-understand areas.
  • For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

@SumanMaharana SumanMaharana requested a review from a team as a code owner March 10, 2026 09:27
@github-actions github-actions Bot added Ingestion safe to test Add this label to run secure Github workflows on PRs labels Mar 10, 2026
gitar-bot[bot]
gitar-bot Bot reviewed Mar 10, 2026
View reviewed changes
Comment thread ingestion/src/metadata/utils/sqlalchemy_utils.py
# Roll back the aborted transaction so the connection remains usable
# for subsequent queries (e.g. get_table_comment). Without this,
# psycopg2 raises InFailedSqlTransaction on every query that follows.
if isinstance(exc, ProgrammingError):
Copy link
Copy Markdown

@gitar-bot gitar-bot Bot Mar 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Edge Case: Rollback only handles ProgrammingError, other DB errors also abort txn

The rollback guard at line 165 only triggers for ProgrammingError, but PostgreSQL/Redshift can abort a transaction on other exception types too (e.g., OperationalError, DatabaseError). Any unhandled aborted transaction will cause the same InFailedSqlTransaction problem for subsequent queries. Since this is inside a broad except Exception block, it would be safer to attempt rollback for any DBAPIError (the base class for all DBAPI-related SQLAlchemy exceptions).

Suggested fix:

from sqlalchemy.exc import DBAPIError
...
        if isinstance(exc, DBAPIError):
            try:
                connection.rollback()
            except Exception:
                pass

Was this helpful? React with 👍 / 👎 | Reply gitar fix to apply this suggestion

gitar-bot[bot]
gitar-bot Bot reviewed Mar 10, 2026
View reviewed changes
Comment thread ingestion/src/metadata/utils/sqlalchemy_utils.py
if isinstance(exc, ProgrammingError):
try:
connection.rollback()
except Exception:
Copy link
Copy Markdown

@gitar-bot gitar-bot Bot Mar 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Quality: Silent pass on rollback failure hides connection issues

The bare except Exception: pass around connection.rollback() silently swallows all errors. If the rollback itself fails, it likely means the connection is broken, which would be useful to log for debugging production issues.

Suggested fix:

try:
    connection.rollback()
except Exception as rollback_exc:
    logger.debug(f"Failed to rollback after DDL error: {rollback_exc}")

Was this helpful? React with 👍 / 👎 | Reply gitar fix to apply this suggestion

@gitar-bot
Copy link
Copy Markdown

gitar-bot Bot commented Mar 10, 2026 •
edited
Loading

🔍 CI failure analysis for 5a008ca: SonarCloud Code Analysis check failed with inaccessible logs—unable to determine the specific code quality issue due to external tool integration limitations.

Overview

The CI analysis identified 1 failure across 1 log. The SonarCloud Code Analysis check failed, but detailed logs are not accessible through the GitHub API since SonarCloud is an external third-party analysis tool that only reports status back to GitHub without exposing underlying analysis details.

Failures

SonarCloud Code Analysis Logs Inaccessible (confidence: high)

  • Type: infrastructure
  • Affected jobs: open-metadata-ingestion SonarCloud Code Analysis (job_id: 66437689518)
  • Related to PR: unclear
  • Root cause: SonarCloud is an external check run that reports status to GitHub but does not expose detailed logs through the GitHub API. The CI infrastructure cannot fetch logs directly from this third-party service.
  • Suggested fix:
    1. Check the SonarCloud dashboard directly at https://sonarcloud.io for the project to view detailed analysis results and quality gate failures
    2. Review any PR annotations or comments posted by SonarCloud on GitHub that may contain specific code quality issues
    3. Verify that SonarCloud quality gates and rules are appropriately configured for the changes in this PR (adds/modifies Redshift DDL handling and database utilities across ingestion source and e2e test files)

Summary

  • PR-related failures: Unable to determine (0 confirmed)
  • Infrastructure/flaky failures: 1 — SonarCloud analysis tool logs inaccessible via API
  • Recommended action: Developer should check the SonarCloud dashboard directly to identify the specific code quality gate failure(s) and address any reported issues in the ingestion source or test code changes.
Code Review ⚠️ Changes requested 0 resolved / 2 findings

Adds PostgreSQL and Redshift DDL and e2e fixes but the rollback error handling is incomplete. The guard at line 165 only catches ProgrammingError while other database exceptions can also abort transactions, and silent exception suppression on rollback failure masks underlying connection issues.

⚠️ Edge Case: Rollback only handles ProgrammingError, other DB errors also abort txn

📄 ingestion/src/metadata/utils/sqlalchemy_utils.py:165

The rollback guard at line 165 only triggers for ProgrammingError, but PostgreSQL/Redshift can abort a transaction on other exception types too (e.g., OperationalError, DatabaseError). Any unhandled aborted transaction will cause the same InFailedSqlTransaction problem for subsequent queries. Since this is inside a broad except Exception block, it would be safer to attempt rollback for any DBAPIError (the base class for all DBAPI-related SQLAlchemy exceptions).

Suggested fix 
from sqlalchemy.exc import DBAPIError
...
        if isinstance(exc, DBAPIError):
            try:
                connection.rollback()
            except Exception:
                pass
💡 Quality: Silent pass on rollback failure hides connection issues

📄 ingestion/src/metadata/utils/sqlalchemy_utils.py:168

The bare except Exception: pass around connection.rollback() silently swallows all errors. If the rollback itself fails, it likely means the connection is broken, which would be useful to log for debugging production issues.

Suggested fix 
try:
    connection.rollback()
except Exception as rollback_exc:
    logger.debug(f"Failed to rollback after DDL error: {rollback_exc}")
🤖 Prompt for agents 
Code Review: Adds PostgreSQL and Redshift DDL and e2e fixes but the rollback error handling is incomplete. The guard at line 165 only catches ProgrammingError while other database exceptions can also abort transactions, and silent exception suppression on rollback failure masks underlying connection issues.

1. ⚠️ Edge Case: Rollback only handles ProgrammingError, other DB errors also abort txn
   Files: ingestion/src/metadata/utils/sqlalchemy_utils.py:165

   The rollback guard at line 165 only triggers for `ProgrammingError`, but PostgreSQL/Redshift can abort a transaction on other exception types too (e.g., `OperationalError`, `DatabaseError`). Any unhandled aborted transaction will cause the same `InFailedSqlTransaction` problem for subsequent queries. Since this is inside a broad `except Exception` block, it would be safer to attempt rollback for any `DBAPIError` (the base class for all DBAPI-related SQLAlchemy exceptions).

   Suggested fix:
   from sqlalchemy.exc import DBAPIError
   ...
           if isinstance(exc, DBAPIError):
               try:
                   connection.rollback()
               except Exception:
                   pass

2. 💡 Quality: Silent pass on rollback failure hides connection issues
   Files: ingestion/src/metadata/utils/sqlalchemy_utils.py:168

   The bare `except Exception: pass` around `connection.rollback()` silently swallows all errors. If the rollback itself fails, it likely means the connection is broken, which would be useful to log for debugging production issues.

   Suggested fix:
   try:
       connection.rollback()
   except Exception as rollback_exc:
       logger.debug(f"Failed to rollback after DDL error: {rollback_exc}")

Tip

Comment Gitar fix CI or enable auto-apply: gitar auto-apply:on

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change:

Auto-apply Compact 
gitar auto-apply:on         

gitar display:verbose

Was this helpful? React with 👍 / 👎 | Gitar

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Mar 10, 2026

🛡️ TRIVY SCAN RESULT 🛡️

Target: openmetadata-ingestion:trivy (debian 12.12)

Vulnerabilities (4)

Package Vulnerability ID Severity Installed Version Fixed Version
libpam-modules CVE-2025-6020 🚨 HIGH 1.5.2-6+deb12u1 1.5.2-6+deb12u2
libpam-modules-bin CVE-2025-6020 🚨 HIGH 1.5.2-6+deb12u1 1.5.2-6+deb12u2
libpam-runtime CVE-2025-6020 🚨 HIGH 1.5.2-6+deb12u1 1.5.2-6+deb12u2
libpam0g CVE-2025-6020 🚨 HIGH 1.5.2-6+deb12u1 1.5.2-6+deb12u2

🛡️ TRIVY SCAN RESULT 🛡️

Target: Java

Vulnerabilities (38)

Package Vulnerability ID Severity Installed Version Fixed Version
com.fasterxml.jackson.core:jackson-core CVE-2025-52999 🚨 HIGH 2.12.7 2.15.0
com.fasterxml.jackson.core:jackson-core GHSA-72hv-8253-57qq 🚨 HIGH 2.12.7 2.18.6, 2.21.1, 3.1.0
com.fasterxml.jackson.core:jackson-core CVE-2025-52999 🚨 HIGH 2.13.4 2.15.0
com.fasterxml.jackson.core:jackson-core GHSA-72hv-8253-57qq 🚨 HIGH 2.13.4 2.18.6, 2.21.1, 3.1.0
com.fasterxml.jackson.core:jackson-core GHSA-72hv-8253-57qq 🚨 HIGH 2.15.2 2.18.6, 2.21.1, 3.1.0
com.fasterxml.jackson.core:jackson-core GHSA-72hv-8253-57qq 🚨 HIGH 2.16.1 2.18.6, 2.21.1, 3.1.0
com.fasterxml.jackson.core:jackson-databind CVE-2022-42003 🚨 HIGH 2.12.7 2.12.7.1, 2.13.4.2
com.fasterxml.jackson.core:jackson-databind CVE-2022-42004 🚨 HIGH 2.12.7 2.12.7.1, 2.13.4
com.google.code.gson:gson CVE-2022-25647 🚨 HIGH 2.2.4 2.8.9
com.google.protobuf:protobuf-java CVE-2021-22569 🚨 HIGH 3.3.0 3.16.1, 3.18.2, 3.19.2
com.google.protobuf:protobuf-java CVE-2022-3509 🚨 HIGH 3.3.0 3.16.3, 3.19.6, 3.20.3, 3.21.7
com.google.protobuf:protobuf-java CVE-2022-3510 🚨 HIGH 3.3.0 3.16.3, 3.19.6, 3.20.3, 3.21.7
com.google.protobuf:protobuf-java CVE-2024-7254 🚨 HIGH 3.3.0 3.25.5, 4.27.5, 4.28.2
com.google.protobuf:protobuf-java CVE-2021-22569 🚨 HIGH 3.7.1 3.16.1, 3.18.2, 3.19.2
com.google.protobuf:protobuf-java CVE-2022-3509 🚨 HIGH 3.7.1 3.16.3, 3.19.6, 3.20.3, 3.21.7
com.google.protobuf:protobuf-java CVE-2022-3510 🚨 HIGH 3.7.1 3.16.3, 3.19.6, 3.20.3, 3.21.7
com.google.protobuf:protobuf-java CVE-2024-7254 🚨 HIGH 3.7.1 3.25.5, 4.27.5, 4.28.2
com.nimbusds:nimbus-jose-jwt CVE-2023-52428 🚨 HIGH 9.8.1 9.37.2
com.squareup.okhttp3:okhttp CVE-2021-0341 🚨 HIGH 3.12.12 4.9.2
commons-beanutils:commons-beanutils CVE-2025-48734 🚨 HIGH 1.9.4 1.11.0
commons-io:commons-io CVE-2024-47554 🚨 HIGH 2.8.0 2.14.0
dnsjava:dnsjava CVE-2024-25638 🚨 HIGH 2.1.7 3.6.0
io.airlift:aircompressor CVE-2025-67721 🚨 HIGH 0.27 2.0.3
io.netty:netty-codec-http2 CVE-2025-55163 🚨 HIGH 4.1.96.Final 4.2.4.Final, 4.1.124.Final
io.netty:netty-codec-http2 GHSA-xpw8-rcwv-8f8p 🚨 HIGH 4.1.96.Final 4.1.100.Final
io.netty:netty-handler CVE-2025-24970 🚨 HIGH 4.1.96.Final 4.1.118.Final
net.minidev:json-smart CVE-2021-31684 🚨 HIGH 1.3.2 1.3.3, 2.4.4
net.minidev:json-smart CVE-2023-1370 🚨 HIGH 1.3.2 2.4.9
org.apache.avro:avro CVE-2024-47561 🔥 CRITICAL 1.7.7 1.11.4
org.apache.avro:avro CVE-2023-39410 🚨 HIGH 1.7.7 1.11.3
org.apache.derby:derby CVE-2022-46337 🔥 CRITICAL 10.14.2.0 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.1.0
org.apache.ivy:ivy CVE-2022-46751 🚨 HIGH 2.5.1 2.5.2
org.apache.mesos:mesos CVE-2018-1330 🚨 HIGH 1.4.3 1.6.0
org.apache.thrift:libthrift CVE-2019-0205 🚨 HIGH 0.12.0 0.13.0
org.apache.thrift:libthrift CVE-2020-13949 🚨 HIGH 0.12.0 0.14.0
org.apache.zookeeper:zookeeper CVE-2023-44981 🔥 CRITICAL 3.6.3 3.7.2, 3.8.3, 3.9.1
org.eclipse.jetty:jetty-server CVE-2024-13009 🚨 HIGH 9.4.56.v20240826 9.4.57.v20241219
org.lz4:lz4-java CVE-2025-12183 🚨 HIGH 1.8.0 1.8.1

🛡️ TRIVY SCAN RESULT 🛡️

Target: Node.js

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: Python

Vulnerabilities (23)

Package Vulnerability ID Severity Installed Version Fixed Version
Authlib CVE-2026-28802 🚨 HIGH 1.6.6 1.6.7
Werkzeug CVE-2024-34069 🚨 HIGH 2.2.3 3.0.3
aiohttp CVE-2025-69223 🚨 HIGH 3.12.12 3.13.3
aiohttp CVE-2025-69223 🚨 HIGH 3.13.2 3.13.3
apache-airflow CVE-2025-68438 🚨 HIGH 3.1.5 3.1.6
apache-airflow CVE-2025-68675 🚨 HIGH 3.1.5 3.1.6, 2.11.1
apache-airflow-providers-http CVE-2025-69219 🚨 HIGH 5.6.0 6.0.0
azure-core CVE-2026-21226 🚨 HIGH 1.37.0 1.38.0
cryptography CVE-2026-26007 🚨 HIGH 42.0.8 46.0.5
google-cloud-aiplatform CVE-2026-2472 🚨 HIGH 1.130.0 1.131.0
google-cloud-aiplatform CVE-2026-2473 🚨 HIGH 1.130.0 1.133.0
jaraco.context CVE-2026-23949 🚨 HIGH 5.3.0 6.1.0
jaraco.context CVE-2026-23949 🚨 HIGH 6.0.1 6.1.0
protobuf CVE-2026-0994 🚨 HIGH 4.25.8 6.33.5, 5.29.6
pyasn1 CVE-2026-23490 🚨 HIGH 0.6.1 0.6.2
python-multipart CVE-2026-24486 🚨 HIGH 0.0.20 0.0.22
ray CVE-2025-62593 🔥 CRITICAL 2.47.1 2.52.0
starlette CVE-2025-62727 🚨 HIGH 0.48.0 0.49.1
urllib3 CVE-2025-66418 🚨 HIGH 1.26.20 2.6.0
urllib3 CVE-2025-66471 🚨 HIGH 1.26.20 2.6.0
urllib3 CVE-2026-21441 🚨 HIGH 1.26.20 2.6.3
wheel CVE-2026-24049 🚨 HIGH 0.45.1 0.46.2
wheel CVE-2026-24049 🚨 HIGH 0.45.1 0.46.2

🛡️ TRIVY SCAN RESULT 🛡️

Target: usr/bin/docker

Vulnerabilities (3)

Package Vulnerability ID Severity Installed Version Fixed Version
stdlib CVE-2025-68121 🔥 CRITICAL v1.25.5 1.24.13, 1.25.7, 1.26.0-rc.3
stdlib CVE-2025-61726 🚨 HIGH v1.25.5 1.24.12, 1.25.6
stdlib CVE-2025-61728 🚨 HIGH v1.25.5 1.24.12, 1.25.6

🛡️ TRIVY SCAN RESULT 🛡️

Target: /etc/ssl/private/ssl-cert-snakeoil.key

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /home/airflow/openmetadata-airflow-apis/openmetadata_managed_apis.egg-info/PKG-INFO

No Vulnerabilities Found

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Mar 10, 2026

🛡️ TRIVY SCAN RESULT 🛡️

Target: openmetadata-ingestion-base-slim:trivy (debian 12.13)

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: Java

Vulnerabilities (37)

Package Vulnerability ID Severity Installed Version Fixed Version
com.fasterxml.jackson.core:jackson-core CVE-2025-52999 🚨 HIGH 2.12.7 2.15.0
com.fasterxml.jackson.core:jackson-core GHSA-72hv-8253-57qq 🚨 HIGH 2.12.7 2.18.6, 2.21.1, 3.1.0
com.fasterxml.jackson.core:jackson-core CVE-2025-52999 🚨 HIGH 2.13.4 2.15.0
com.fasterxml.jackson.core:jackson-core GHSA-72hv-8253-57qq 🚨 HIGH 2.13.4 2.18.6, 2.21.1, 3.1.0
com.fasterxml.jackson.core:jackson-core GHSA-72hv-8253-57qq 🚨 HIGH 2.15.2 2.18.6, 2.21.1, 3.1.0
com.fasterxml.jackson.core:jackson-databind CVE-2022-42003 🚨 HIGH 2.12.7 2.12.7.1, 2.13.4.2
com.fasterxml.jackson.core:jackson-databind CVE-2022-42004 🚨 HIGH 2.12.7 2.12.7.1, 2.13.4
com.google.code.gson:gson CVE-2022-25647 🚨 HIGH 2.2.4 2.8.9
com.google.protobuf:protobuf-java CVE-2021-22569 🚨 HIGH 3.3.0 3.16.1, 3.18.2, 3.19.2
com.google.protobuf:protobuf-java CVE-2022-3509 🚨 HIGH 3.3.0 3.16.3, 3.19.6, 3.20.3, 3.21.7
com.google.protobuf:protobuf-java CVE-2022-3510 🚨 HIGH 3.3.0 3.16.3, 3.19.6, 3.20.3, 3.21.7
com.google.protobuf:protobuf-java CVE-2024-7254 🚨 HIGH 3.3.0 3.25.5, 4.27.5, 4.28.2
com.google.protobuf:protobuf-java CVE-2021-22569 🚨 HIGH 3.7.1 3.16.1, 3.18.2, 3.19.2
com.google.protobuf:protobuf-java CVE-2022-3509 🚨 HIGH 3.7.1 3.16.3, 3.19.6, 3.20.3, 3.21.7
com.google.protobuf:protobuf-java CVE-2022-3510 🚨 HIGH 3.7.1 3.16.3, 3.19.6, 3.20.3, 3.21.7
com.google.protobuf:protobuf-java CVE-2024-7254 🚨 HIGH 3.7.1 3.25.5, 4.27.5, 4.28.2
com.nimbusds:nimbus-jose-jwt CVE-2023-52428 🚨 HIGH 9.8.1 9.37.2
com.squareup.okhttp3:okhttp CVE-2021-0341 🚨 HIGH 3.12.12 4.9.2
commons-beanutils:commons-beanutils CVE-2025-48734 🚨 HIGH 1.9.4 1.11.0
commons-io:commons-io CVE-2024-47554 🚨 HIGH 2.8.0 2.14.0
dnsjava:dnsjava CVE-2024-25638 🚨 HIGH 2.1.7 3.6.0
io.airlift:aircompressor CVE-2025-67721 🚨 HIGH 0.27 2.0.3
io.netty:netty-codec-http2 CVE-2025-55163 🚨 HIGH 4.1.96.Final 4.2.4.Final, 4.1.124.Final
io.netty:netty-codec-http2 GHSA-xpw8-rcwv-8f8p 🚨 HIGH 4.1.96.Final 4.1.100.Final
io.netty:netty-handler CVE-2025-24970 🚨 HIGH 4.1.96.Final 4.1.118.Final
net.minidev:json-smart CVE-2021-31684 🚨 HIGH 1.3.2 1.3.3, 2.4.4
net.minidev:json-smart CVE-2023-1370 🚨 HIGH 1.3.2 2.4.9
org.apache.avro:avro CVE-2024-47561 🔥 CRITICAL 1.7.7 1.11.4
org.apache.avro:avro CVE-2023-39410 🚨 HIGH 1.7.7 1.11.3
org.apache.derby:derby CVE-2022-46337 🔥 CRITICAL 10.14.2.0 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.1.0
org.apache.ivy:ivy CVE-2022-46751 🚨 HIGH 2.5.1 2.5.2
org.apache.mesos:mesos CVE-2018-1330 🚨 HIGH 1.4.3 1.6.0
org.apache.thrift:libthrift CVE-2019-0205 🚨 HIGH 0.12.0 0.13.0
org.apache.thrift:libthrift CVE-2020-13949 🚨 HIGH 0.12.0 0.14.0
org.apache.zookeeper:zookeeper CVE-2023-44981 🔥 CRITICAL 3.6.3 3.7.2, 3.8.3, 3.9.1
org.eclipse.jetty:jetty-server CVE-2024-13009 🚨 HIGH 9.4.56.v20240826 9.4.57.v20241219
org.lz4:lz4-java CVE-2025-12183 🚨 HIGH 1.8.0 1.8.1

🛡️ TRIVY SCAN RESULT 🛡️

Target: Node.js

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: Python

Vulnerabilities (9)

Package Vulnerability ID Severity Installed Version Fixed Version
apache-airflow CVE-2025-68438 🚨 HIGH 3.1.5 3.1.6
apache-airflow CVE-2025-68675 🚨 HIGH 3.1.5 3.1.6, 2.11.1
cryptography CVE-2026-26007 🚨 HIGH 42.0.8 46.0.5
jaraco.context CVE-2026-23949 🚨 HIGH 6.0.1 6.1.0
starlette CVE-2025-62727 🚨 HIGH 0.48.0 0.49.1
urllib3 CVE-2025-66418 🚨 HIGH 1.26.20 2.6.0
urllib3 CVE-2025-66471 🚨 HIGH 1.26.20 2.6.0
urllib3 CVE-2026-21441 🚨 HIGH 1.26.20 2.6.3
wheel CVE-2026-24049 🚨 HIGH 0.45.1 0.46.2

🛡️ TRIVY SCAN RESULT 🛡️

Target: /etc/ssl/private/ssl-cert-snakeoil.key

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/extended_sample_data.yaml

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/lineage.yaml

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/sample_data.json

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/sample_data.yaml

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/sample_data_aut.yaml

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/sample_usage.json

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/sample_usage.yaml

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: /ingestion/pipelines/sample_usage_aut.yaml

No Vulnerabilities Found

@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Mar 10, 2026

Quality Gate Failed Quality Gate failed for 'open-metadata-ingestion'

Failed conditions
18.2% Coverage on New Code (required ≥ 20%)

See analysis details on SonarQube Cloud

@SumanMaharana SumanMaharana merged commit a0a228f into main Mar 10, 2026
38 of 40 checks passed
@SumanMaharana SumanMaharana deleted the postgres-fixes branch March 10, 2026 12:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@gitar-bot gitar-bot[bot] gitar-bot[bot] left review comments

@ulixius9 ulixius9 ulixius9 approved these changes

@mohittilala mohittilala mohittilala approved these changes

Assignees

No one assigned

Labels

Ingestion safe to test Add this label to run secure Github workflows on PRs

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@SumanMaharana @ulixius9 @mohittilala