Release7.2.5.10
This release introduces key enhancements and bug fixes across Query Sheet, Lineage, Connectors, Application APIs, Data Access Management, and Advanced Jobs, improving query reliability, lineage completeness, metadata extraction, API accuracy, access synchronization, and job execution consistency.
Key Highlights
Query Sheet (AWS Aurora): Fixed query execution failures for AWS Aurora (MySQL and PostgreSQL) connections, ensuring queries return expected results without missing response errors.
Lineage (Amazon QuickSight):
Resolved missing lineage between source systems and QuickSight datasets, ensuring complete lineage visibility.
Fixed incorrect column mapping in custom SQL queries to accurately reflect lineage relationships.
Corrected lineage status handling to properly identify source and temporary tables and display accurate lineage results.
Connectors (Kafka):
Power BI: Added support for metadata retrieval from reports deployed via Deployment Pipelines, enabling complete metadata and column-level lineage extraction.
Kafka: Fixed Kerberos authentication validation failures, ensuring successful connection validation.
Oracle BI Publisher: Resolved connection validation errors to allow successful connector setup.
Application APIs:
Fixed the GET /api/tags/open endpoint to return the correct list of tags based on provided parameters.
Corrected Reports API response to include the has_lineage field and display accurate lineage status.
Data Access Management: Fixed user and role crawling issues to ensure successful retrieval from the DAM screen.
Advanced Jobs: Resolved missing mapping generation in Mapping AD jobs and fixed log export functionality to ensure mappings are created, and logs are downloadable.
Release Details:
Hotfix Release
Release7.2.5.10
Release7.2.5.10.725101d308dd
April 24, 2026
Query Sheet
Fixed
Fixed Query Execution Issue for AWS Aurora Connections
In the Query Sheet, an issue where queries failed to return data for AWS Aurora (MySQL and PostgreSQL) connections has been resolved. Query execution returned an error indicating the response was missing, and no results were displayed.
The execution logic has been corrected to ensure queries run successfully and return the expected data.
Lineage
Fixed
Resolved Missing Lineage in QuickSight Reports
In Amazon QuickSight, an issue where lineage was not built between source data and QuickSight datasets for certain reports has been resolved. Some reports did not show any connection between the source and the dataset, resulting in incomplete lineage.
The logic has been corrected to ensure lineage is properly created and displayed from source systems to QuickSight datasets.
QuickSight Custom SQL Column Mapping Fix
In Amazon QuickSight, an issue where columns in custom SQL queries were not mapped correctly has been resolved. Some columns did not link properly according to the query logic, resulting in incorrect lineage mapping.
The mapping logic has been corrected to ensure columns are accurately linked and reflected in lineage.
Resolved Incorrect Lineage Status in QuickSight
In Amazon QuickSight, an issue in which lineage results were displayed incorrectly has been resolved. Some source tables were wrongly treated as temporary tables. Temporary tables were marked as successful lineage, and valid lineage between objects was sometimes shown as failed.
The lineage processing has been corrected to properly identify source tables, accurately handle temporary tables, and display the correct lineage status.
Connectors
Improved
Enhanced Metadata Retrieval for Power BI Reports Deployed via Deployment Pipelines
In the Power BI connector, reports deployed via Deployment Pipelines were not accessible during crawling, resulting in incomplete metadata and missing column-level details in OvalEdge. This limitation affected data lineage visibility, impact analysis, and overall metadata accuracy.
With this improvement, support is introduced to enable PBIX extraction or equivalent metadata retrieval for reports deployed via Deployment Pipelines. This ensures that complete report metadata, including column-level details, is available during crawling, regardless of the deployment method.
Fixed
Resolved Kerberos Authentication Validation Failure in Kafka
In Kafka Connection, an issue where connection validation failed when using Kerberos authentication has been resolved. The validation process failed even with the correct configuration, preventing connection to the Kafka cluster. The system could not load the required authentication settings, which caused the validation to stop.
The configuration handling has been corrected to load authentication settings, allowing for successful connection validation.
Resolved Connection Validation Failure in Oracle BI Publisher
In Oracle BI Publisher Connector, an issue where connection validation failed with an error has been resolved. The validation process did not complete successfully and returned an error during the check.
The validation logic has been corrected to ensure the connection can be validated successfully.
Application APIs
Fixed
Resolved Issue with Tags Not Returned by API
In APIs, an issue with the GET /api/tags/open endpoint not returning the expected list of tags has been resolved. The API failed to return data even when valid parameters such as offset and limit were provided.
The API has been fixed to return the correct list of tags based on the given parameters.
Fixed Missing has_lineage Field in Reports API
In the Reports API, an issue where the lineage status was incorrectly displayed in the Report/{reportId} response has been resolved. The response did not include the has_lineage field and instead showed build_lineage as false, even when lineage existed for the report.
The API response has been corrected to include the has_lineage field and to display the accurate lineage status.
Data Access Management
Fixed
Resolved User and Role Crawling Issue in DAM
In Data Access Management, an issue where users and roles could not be crawled from the DAM screen has been resolved. Connection validation worked successfully, but crawling failed due to a connection error.
The connection handling has been corrected to ensure users and roles are successfully crawled from the DAM screen.
Advanced Jobs
Fixed
Resolved Missing Mappings in Mapping AD Job
In Advanced Jobs, an issue in which the Mapping AD job completed successfully but did not create any mappings has been resolved. The job finished without errors, but no mappings were generated. In addition, exporting the job logs did not produce any file.
The job processing and log export functions have been corrected to ensure mappings are created as expected, and logs are properly downloaded.
Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?