Release6.0.2.30

OvalEdge Release6.0.2.30 is a hotfix release that includes improvements to the Connectors module and in this release, the critical and significant bugs associated with the Data Catalog, Business Glossary, Advanced Tools, Administration, and Connectors modules are fixed and working as expected.

Improvements

Connectors

• Azure Data Factory (ADF) is now integrated into pipelines with Databricks notebook activities, so that the lineage associations are established to track data flow accurately through Databricks, ensuring data provenance and compliance. This enables a clear understanding of how data moves from source to destination, even when passing through Databricks notebooks.

Bug Fixes

The following bugs have been fixed in this release, and the application is working as expected.

Data Catalog

• In the Data Catalog, previous tabs did not hide when users selected a different tab in the lower portion of the view, which made it appear as if the page was not working. This issue has been resolved, and now, when users select a different tab in the lower portion of the view, the previous tabs are hidden appropriately.
• For the Teradata connector, The connector was not able to crawl source descriptions for some views and tables in production. This issue has been resolved and the descriptions are now visible in the source description column.
• The table columns were not being populated correctly in the OvalEdge application. This was causing a mismatch between the number of columns displayed in the UI and the actual number of columns present in the table. The issue has been resolved and the columns displayed in the application and the actual number of columns present in the table are now the same.

Business Glossary

• In the Business Glossary, users were unable to view the field details on the Term summary page. This issue has been resolved, and users can now access and view the field details on the summary page.

Advanced Tools

• When users attempted to download the DQR with the data template from Load metadata files, the custom field names were not in sequential order. This issue has been resolved and the custom field names are now in the correct order when users download the DQR with data template from Load metadata files.

Lineage

• The lineage for some source objects is incomplete, which prevents the user from having a complete view of their data. The new connector ensures that all necessary objects are included in the lineage, improving the user's ability to troubleshoot.
• The user was unable to parse queries related to used vehicles due to a problem with the data in their machine environment. This issue has been resolved and the user is able to parse queries related to used vehicles.
• Previously, users couldn't directly download it to their local machines. The source code was exported to the temporary path of the instance. To address this, a request was made to modify the export process. The new approach involves triggering a job when the source code is exported. Once the job is finished, a link is generated for the user to click on it and download the source code directly to their local machine. This issue has been resolved and the source code can be downloaded to the user's local machine.
• The query presents two destinations and only one source, resulting in an incomplete lineage representation. This issue has been resolved and the query will be able to present the correct number of sources and destinations.

Administration

• In Security, the admin user was unable to view the OvalEdge database at the security level, preventing them from hiding the database from a public user. This was because the admin user had permission to view the database at the data catalog level, but not at the security level. The issue has been resolved and admin users can now view the database at the security level to update the permissions.
• In Security, users could not delete DAGs that were added using the Tag button inside the object summary page. This issue has been resolved and the users are able to delete the DAGs that were added to the data objects using the Tag button.
• In Custom Fields, the date format for the /api/query/update (POST) endpoint was inconsistent with other APIs. This could affect data processing and require investigation to ensure alignment. The issue has been resolved and the date format for the API query is now consistent with other APIs.
• In Security, Users with the Preview and Analyst roles were not able to see the terms and tags list in the filter because they did not have the necessary permissions. The issue has been resolved by granting the Preview and Analyst roles the necessary permissions from security.

Connectors

• For the S3 connector, users were unable to view data columns for S3 Parquet files because the struct data type was not being handled. This issue has been resolved by adding support for struct data types. Users are now able to view data columns for S3 Parquet files.
  

Copyright © 2023, OvalEdge LLC, Peachtree Corners, GA USA