Add stored procedures and functions support to MySQL connector #25182

Copilot · 2026-01-09T11:08:29Z

Describe your changes:

MySQL connector now ingests stored procedures and functions

Type of change:

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.

The issue properly describes why the new feature is needed, what's the goal, and how we are building it. Any discussion or decision-making process is reflected in the issue.
I have updated the documentation.
I have added tests around the new logic.

Original prompt

This section details on the original issue you should resolve

<issue_title>Support Stored Procedures & Functions in MySQL Connector</issue_title>
<issue_description>Feature
Add support for stored procedures and stored functions in the MySQL connector.

Describe the task
Currently, the MySQL connector in OpenMetadata does not support the ingestion of stored procedures and stored functions. As a result, these routines and their associated metadata are missing from the platform. The task is to add support for ingesting both stored procedures and stored functions in the MySQL connector to provide more complete metadata coverage

We already have support for postgres connector</issue_description>

<agent_instructions>Also add unit tests for the changes in @test_mysql.py</agent_instructions>

Comments on the Issue (you are @copilot in this section)

Fixes Support Stored Procedures & Functions in MySQL Connector #25121

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

- Created models.py with MysqlStoredProcedure model and STORED_PROC_LANGUAGE_MAP - Added queries for fetching stored procedures and functions from information_schema - Implemented get_stored_procedures() and yield_stored_procedure() methods in MysqlSource - Added comprehensive unit tests in test_mysql.py - Code formatted with black and isort Co-authored-by: SumanMaharana <59608519+SumanMaharana@users.noreply.github.com>

gitar-bot · 2026-01-09T11:21:13Z

Implementation Summary

The MySQL stored procedures and functions support has been successfully implemented following the PostgreSQL reference pattern. Here's what was completed:

Files Created/Modified

✅ NEW: ingestion/src/metadata/ingestion/source/database/mysql/models.py

Created MysqlStoredProcedure model with fields: name, schema, definition, language, procedure_type, description
Added STORED_PROC_LANGUAGE_MAP for SQL language mapping

✅ MODIFIED: ingestion/src/metadata/ingestion/source/database/mysql/queries.py

Added MYSQL_GET_STORED_PROCEDURES query for ROUTINE_TYPE = 'PROCEDURE'
Added MYSQL_GET_FUNCTIONS query for ROUTINE_TYPE = 'FUNCTION'
Both queries fetch from information_schema.ROUTINES

✅ MODIFIED: ingestion/src/metadata/ingestion/source/database/mysql/metadata.py

Implemented get_stored_procedures() method that fetches both procedures and functions
Implemented yield_stored_procedure() method that creates CreateStoredProcedureRequest
Added _get_stored_procedures_internal() helper method with proper error handling
Respects includeStoredProcedures configuration flag

✅ MODIFIED: ingestion/tests/unit/topology/database/test_mysql.py

Added test_get_stored_procedures() - tests fetching procedures and functions
Added test_get_stored_procedures_disabled() - tests configuration flag
Added test_yield_stored_procedure() - tests request creation
Added test_yield_stored_procedure_with_error() - tests error handling

Key Features

✅ Distinguishes between stored procedures and functions using procedure_type
✅ Fetches procedure definitions and descriptions from information_schema.ROUTINES
✅ Proper error handling with StackTraceError and logging
✅ Configuration-driven with includeStoredProcedures flag
✅ Comprehensive unit test coverage (4 test cases)
✅ Follows existing codebase patterns from PostgreSQL connector

Testing Status

Unit tests added and structured correctly
Mock-based testing for database interactions
Error handling scenarios covered

Next Steps

The checklist shows:

✅ Research and understand PostgreSQL implementation
✅ Create MySQL queries for stored procedures and functions
✅ Create MySQL models.py file with data structures
✅ Update MySQL metadata.py with stored procedure methods
✅ Add unit tests in test_mysql.py
✅ Format code with black and isort
⏳ Test the implementation manually
⏳ Run code quality checks

Ready for code quality verification and manual testing!

ingestion/src/metadata/ingestion/source/database/mysql/metadata.py

github-actions · 2026-01-09T11:23:06Z

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

github-actions · 2026-01-09T12:52:36Z

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

…hub.com:open-metadata/OpenMetadata into copilot/add-support-stored-procedures-functions

gitar-bot · 2026-01-09T15:21:32Z

🔍 CI failure analysis for 169ec4a: Multiple unrelated CI failures: PostgreSQL lineage test and Playwright E2E tests. MySQL tests passed successfully.

Issue

Multiple CI jobs have failed:

py-run-tests (3.10) - Python unit tests (job IDs: 59924317108, 59924320947)
playwright-ci-postgresql (3, 6) - Playwright E2E tests (job ID: 59924333026)

Root Cause

All failures are completely unrelated to the MySQL stored procedures changes in this PR.

Details

Python unit test failures:

Both runs failed on test_complex_postgres_view in ingestion/tests/unit/lineage/queries/test_specific_dialect_queries.py
This tests PostgreSQL view lineage parsing, not MySQL functionality
MySQL unit tests in test_mysql.py passed successfully (2 tests) in both runs
Consistent failure pattern indicates a pre-existing issue in main branch

Playwright E2E test failure:

Failed in "Run Playwright tests" step
Playwright tests are UI/frontend integration tests
This PR only modifies Python backend code for MySQL connector:
- mysql/metadata.py
- mysql/models.py
- mysql/queries.py
- mysql/test_mysql.py
No frontend/UI code was touched
No changes to any TypeScript, React, or UI components

Modified files scope:
All changes are isolated to Python ingestion layer for MySQL:

Backend connector implementation
Data models
SQL queries
Unit tests

None of these affect:

Frontend UI (Playwright tests)
PostgreSQL lineage parsing (Python unit test failure)

Conclusion

Both CI failures are unrelated to this PR's MySQL stored procedures implementation:

Python test failure: Pre-existing bug in PostgreSQL lineage parsing on main branch
Playwright test failure: Frontend E2E test issue unrelated to backend MySQL connector changes

The MySQL implementation is working correctly as evidenced by all MySQL-specific tests passing. This PR should not be blocked by unrelated test failures in PostgreSQL lineage parsing and frontend E2E tests.

Code Review 👍 Approved with suggestions

Clean implementation of stored procedures support for MySQL. Two previous findings remain relevant: SQL query uses string formatting (should use parameterized queries), and language mapping returns None for unknown languages.

⚠️

Security: SQL injection risk via string formatting in queries

📄 ingestion/src/metadata/ingestion/source/database/mysql/metadata.py:88-96

The SQL queries use Python string formatting (.format()) to interpolate schema_name directly into the query string:

MYSQL_GET_STORED_PROCEDURES.format(schema_name=self.context.get().database_schema)

While database_schema comes from the internal context and is less likely to be directly user-controlled, this pattern is inherently risky and inconsistent with secure coding practices. If the schema name contains special characters or is somehow manipulated, it could lead to SQL injection.

Recommended Fix: Use parameterized queries instead:

query = """
SELECT ROUTINE_NAME AS procedure_name, ...
FROM information_schema.ROUTINES
WHERE ROUTINE_TYPE = 'PROCEDURE'
AND ROUTINE_SCHEMA = :schema_name
"""
results = self.engine.execute(query, {"schema_name": schema_name}).all()

Alternatively, use SQLAlchemy's text() with bound parameters for proper escaping.

More details 💡 1 suggestion ✅ 1 resolved

💡 Edge Case: Language mapping fallback returns None for unknown languages

📄 ingestion/src/metadata/ingestion/source/database/mysql/models.py:20-22 📄 ingestion/src/metadata/ingestion/source/database/mysql/metadata.py:130

The STORED_PROC_LANGUAGE_MAP only maps "SQL" to Language.SQL. For stored procedures written in other languages or when the language field has an unexpected value, STORED_PROC_LANGUAGE_MAP.get(stored_procedure.language) will return None.

storedProcedureCode=StoredProcedureCode(
    language=STORED_PROC_LANGUAGE_MAP.get(stored_procedure.language),  # Could be None
    code=stored_procedure.definition,
),

While MySQL primarily uses SQL for stored procedures, the ROUTINE_BODY field in information_schema.ROUTINES can technically have different values. Returning None may cause issues downstream if the language field is expected to be set.

Recommended Fix: Either provide a default fallback:

language=STORED_PROC_LANGUAGE_MAP.get(stored_procedure.language, Language.SQL)

Or log a warning when encountering an unknown language.

✅ Bug: Inconsistent dict access patterns may cause KeyError

📄 ingestion/src/metadata/ingestion/source/database/mysql/metadata.py:94-99
In _get_stored_procedures_internal, the error handling code uses dict(row) to access procedure_name:
logger.warning(f"Error parsing stored procedure: {dict(row).get('procedure_name', 'UNKNOWN')}")
self.status.failed(
    error=StackTraceError(
        name=dict(row).get("procedure_name", "UNKNOWN"),
        ...
    )
)
However, when iterating the row, the successful path accesses row._mapping. The dict(row) conversion may not work consistently with the SQLAlchemy result row type, especially in different SQLAlchemy versions. This could cause a silent failure where the procedure name shows as "UNKNOWN" even when it's available.

Recommended Fix: Use consistent access patterns:
row_dict = dict(row._mapping)
# Then use row_dict.get("procedure_name", "UNKNOWN") in both success and error paths

What Works Well

Good error handling with proper logging and status tracking. Follows the existing PostgreSQL connector pattern. Comprehensive unit tests covering fetch, disabled state, and model validation scenarios.

Recommendations

Consider using SQLAlchemy's text() with bound parameters instead of string formatting for the MYSQL_GET_ROUTINES query to follow security best practices, even though the input is internally controlled.

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 Hiding non-applicable rules.

Comment with these commands to change:

`Auto-apply`	`Compact`
`gitar auto-apply:on`	`gitar display:verbose`

_{Was this helpful? React with 👍 / 👎 | This comment will update automatically (Docs)}

github-actions · 2026-01-09T15:28:29Z

🛡️ TRIVY SCAN RESULT 🛡️

Target: `openmetadata-ingestion-base-slim:trivy (debian 12.12)`

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: `Java`

Vulnerabilities (33)

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`	CVE-2025-52999	🚨 HIGH	2.13.4	2.15.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.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 (4)

Package	Vulnerability ID	Severity	Installed Version	Fixed Version
`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

🛡️ 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

github-actions · 2026-01-09T15:29:08Z

🛡️ TRIVY SCAN RESULT 🛡️

Target: `openmetadata-ingestion:trivy (debian 12.12)`

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: `Java`

Vulnerabilities (33)

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`	CVE-2025-52999	🚨 HIGH	2.13.4	2.15.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.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
`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
`deepdiff`	CVE-2025-58367	🔥 CRITICAL	7.0.1	8.6.1
`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

🛡️ 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

Initial plan

77d8646

Copilot AI assigned Copilot and SumanMaharana Jan 9, 2026

Copilot started work on behalf of SumanMaharana January 9, 2026 11:08 View session

keshavmohta09 self-assigned this Jan 9, 2026

keshavmohta09 requested a review from a team January 9, 2026 11:09

Copilot AI changed the title ~~[WIP] Add support for stored procedures and functions in MySQL connector~~ Add stored procedures and functions support to MySQL connector Jan 9, 2026

Copilot AI requested a review from SumanMaharana January 9, 2026 11:21

Copilot finished work on behalf of SumanMaharana January 9, 2026 11:21

gitar-bot bot reviewed Jan 9, 2026

View reviewed changes

ingestion/src/metadata/ingestion/source/database/mysql/metadata.py Outdated Show resolved Hide resolved

gitar-bot bot reviewed Jan 9, 2026

View reviewed changes

ingestion/src/metadata/ingestion/source/database/mysql/metadata.py Outdated Show resolved Hide resolved

Merge branch 'main' into copilot/add-support-stored-procedures-functions

239758a

keshavmohta09 added safe to test Add this label to run secure Github workflows on PRs Ingestion labels Jan 9, 2026

fix: code optimization and tests

036680c

keshavmohta09 mentioned this pull request Jan 9, 2026

Docs: MySQL Stored Procedures open-metadata/docs-v1#630

Merged

Merge branch 'copilot/add-support-stored-procedures-functions' of git…

8f55e24

…hub.com:open-metadata/OpenMetadata into copilot/add-support-stored-procedures-functions

keshavmohta09 added the To release Will cherry-pick this PR into the release branch label Jan 9, 2026

keshavmohta09 marked this pull request as ready for review January 9, 2026 15:17

keshavmohta09 had a problem deploying to test January 9, 2026 15:17 — with GitHub Actions Error

Merge branch 'main' into copilot/add-support-stored-procedures-functions

169ec4a

keshavmohta09 temporarily deployed to test January 9, 2026 15:17 — with GitHub Actions Inactive

keshavmohta09 had a problem deploying to test January 9, 2026 15:17 — with GitHub Actions Failure

keshavmohta09 temporarily deployed to test January 9, 2026 15:17 — with GitHub Actions Inactive

keshavmohta09 had a problem deploying to test January 9, 2026 15:17 — with GitHub Actions Failure

keshavmohta09 temporarily deployed to test January 9, 2026 15:17 — with GitHub Actions Inactive

keshavmohta09 unassigned SumanMaharana Jan 9, 2026

harshsoni2024 approved these changes Jan 9, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Add stored procedures and functions support to MySQL connector #25182

Add stored procedures and functions support to MySQL connector #25182

Uh oh!

Copilot AI commented Jan 9, 2026 •

edited by keshavmohta09

Loading

Uh oh!

gitar-bot bot commented Jan 9, 2026

Uh oh!

Uh oh!

Uh oh!

github-actions bot commented Jan 9, 2026

Uh oh!

github-actions bot commented Jan 9, 2026

Uh oh!

gitar-bot bot commented Jan 9, 2026 •

edited

Loading

Issue

Root Cause

Details

Conclusion

What Works Well

Recommendations

Uh oh!

github-actions bot commented Jan 9, 2026

Uh oh!

github-actions bot commented Jan 9, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Add stored procedures and functions support to MySQL connector #25182

Are you sure you want to change the base?

Add stored procedures and functions support to MySQL connector #25182

Uh oh!

Conversation

Copilot AI commented Jan 9, 2026 • edited by keshavmohta09 Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Describe your changes:

Type of change:

Checklist:

Comments on the Issue (you are @copilot in this section)

Uh oh!

gitar-bot bot commented Jan 9, 2026

Implementation Summary

Files Created/Modified

Key Features

Testing Status

Next Steps

Uh oh!

Uh oh!

Uh oh!

github-actions bot commented Jan 9, 2026

Uh oh!

github-actions bot commented Jan 9, 2026

Uh oh!

gitar-bot bot commented Jan 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Issue

Root Cause

Details

Conclusion

What Works Well

Recommendations

Uh oh!

github-actions bot commented Jan 9, 2026

🛡️ TRIVY SCAN RESULT 🛡️

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

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: Java

Vulnerabilities (33)

🛡️ TRIVY SCAN RESULT 🛡️

Target: Node.js

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Target: Python

Vulnerabilities (4)

🛡️ 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

Uh oh!

github-actions bot commented Jan 9, 2026

🛡️ TRIVY SCAN RESULT 🛡️

Target: openmetadata-ingestion:trivy (debian 12.12)

No Vulnerabilities Found

🛡️ TRIVY SCAN RESULT 🛡️

Copilot AI commented Jan 9, 2026 •

edited by keshavmohta09

Loading

gitar-bot bot commented Jan 9, 2026 •

edited

Loading

Target: `openmetadata-ingestion-base-slim:trivy (debian 12.12)`

Target: `Java`

Target: `Node.js`

Target: `Python`

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

Target: `/ingestion/pipelines/extended_sample_data.yaml`

Target: `/ingestion/pipelines/lineage.yaml`

Target: `/ingestion/pipelines/sample_data.json`

Target: `/ingestion/pipelines/sample_data.yaml`

Target: `/ingestion/pipelines/sample_data_aut.yaml`

Target: `/ingestion/pipelines/sample_usage.json`

Target: `/ingestion/pipelines/sample_usage.yaml`

Target: `/ingestion/pipelines/sample_usage_aut.yaml`

Target: `openmetadata-ingestion:trivy (debian 12.12)`

Target: `Java`

Target: `Node.js`

Target: `Python`

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

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