> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/patch-releases/release8.2.4.md).
# Release8.2.4
This release introduces key enhancements and bug fixes across Lineage and Connectors, improving pipeline lineage generation, lineage build reliability, database connectivity, metadata cataloging, and report identification.
**Key Highlights**
* **Lineage**:
* Fixed ADF pipeline lineage generation to correctly identify available source and target details from Pipeline Runs and create the expected source-to-target relationships.
* Resolved JSON parsing errors during Airflow lineage builds, ensuring lineage generation completes successfully after connector crawling.
* **Connectors**:
* **SingleStore**: Added dedicated SingleStore connector support for connection management, metadata crawling, profiling, and cataloging of supported SingleStore objects.
* **Temenos SSRS**: Added support for meaningful Temenos SSRS report names by retrieving business-friendly names from the Temenos database and using them as Asset Titles during crawling.
**Release Details:**
| Release Type | Release Version | Build <Release. Build Number. Release Stamp> | Build Date |
|---|
| Patch Release | Release8.2.4 | release8.2.4.824.7e9b9f1 | September 30, 2026 |
## Lineage
### Fixed
**Resolved Missing ADF Pipeline Lineage**
In ADF, an issue where pipeline lineage was not generated even when both source and target details were available in the Pipeline Run has been resolved. The lineage process did not correctly identify the available source and target details. As a result, it did not create the expected source-to-target relationship.
The issue has been fixed to ensure lineage is generated when both source and target details are available in the Pipeline Run.
**Resolved Airflow Lineage Build JSON Parsing Error**
In Airflow, an issue where building lineage failed with a JSON parsing error has been resolved. The lineage build job failed after the Airflow connector was crawled successfully and Build Lineage was started.
The lineage build process now handles the data correctly and completes without the parsing error.
## Connectors
### New & Improved
**SingleStore Connector Support**
OvalEdge now supports SingleStore as a dedicated connector, enabling users to connect to SingleStore, crawl metadata, profile data, and catalog supported data assets. The connector provides configuration and management options similar to the existing MySQL connector, while supporting SingleStore-specific capabilities where applicable.
The following enhancements have been implemented:
* Users can create, edit, validate, save, rename, and delete SingleStore connectors.
* Connection configuration supports authentication, server, port, database, credentials, connection string, plugin details, governance roles, and Bridge selection.
* Users can configure crawler rules to include or exclude schemas, tables, views, columns, procedures, and functions.
* Metadata crawling supports databases, tables, views, columns, procedures, functions, source code, and indexes.
* Profiling is supported based on the existing MySQL connector capabilities, where applicable.
* Applicable settings for Query Policies, Access Instructions, Business Glossary, Anomaly Detection, Connection Pooling, and other connector options are supported.
* Users can perform connector actions such as Crawl and Profile and manage connector settings through the 9-dots menu.
* Supported SingleStore objects, including databases, tables, views, columns, and indexes, can be cataloged in the Data Catalog.
* Authorized users can view SingleStore objects and their associated metadata based on their metadata access permissions.
**Meaningful Report Names for Temenos SSRS Reports**
Temenos SSRS reports were previously cataloged in OvalEdge using GUID-based values from the SSRS report path as the Asset Title. These values did not provide meaningful information about the report, making it difficult for users to identify reports in the Data Catalog.
With this enhancement, the SSRS connector now supports a Temenos Catalog option that allows administrators to reference an existing Temenos SQL Server connection. During crawling, the connector retrieves the corresponding business-friendly report names from the Temenos database and uses them as the OvalEdge Asset Titles.
The following enhancements have been implemented:
* A new Catalog Type option supports Regular Catalog and Temenos Catalog.
* Existing SSRS crawling behavior remains unchanged for Regular Catalog.
* Temenos Catalog allows administrators to select an existing Temenos SQL Server connection configured in OvalEdge.
* Business-friendly report names are retrieved from the Temenos database during crawling.
* Retrieved report names are used as the Asset Title instead of GUID-based SSRS path values.
* If no matching Temenos report is found, the existing SSRS-derived report name is retained.
* Blank or null Temenos report names do not overwrite an existing valid Asset Title.
* Changes to report names in the Temenos database are reflected during subsequent successful crawls.
* Database connectivity, query, and report mapping issues are recorded in the standard connector logs.
***
Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ovaledge.com/patch-releases/release8.2.4.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.