Connectors

In Connectors, Data Quality is enabled only for supported connectors during creation.
What Changed
In connectors, the system did not restrict Data Quality configuration based on connector compatibility, which could allow the selection of unsupported connectors. Now, only connectors that support Data Quality are enabled during connector creation. Connectors that do not support Data Quality remain disabled, consistent with the behavior for Lineage and RDAM. This ensures proper configuration and prevents the selection of incompatible connectors.
Affected Users: Administrators
In Connectors, the crawl process for SQL, Oracle, and Greenplum connectors now retrieves index and constraint details along with other metadata.
What Changed
In connectors, the crawl process retrieved only general metadata such as schemas, tables, and columns, omitting index and constraint details from the source databases. Now, after validating the connection and initiating the crawl, index and constraint information is also captured and included in the crawl results. This enhancement provides a more complete view of database metadata.
Affected Users: Administrators
In Connectors, licensing for each connection is now calculated using a unique field assigned to the connection instead of the connector’s IP address.
What Changed
In connectors, licensing for each connection was determined based on the connector’s IP address. Connectors without an IP address could not be identified accurately, leading to incorrect license counts. Now, a unique field assigned to each connection is used for licensing calculations, ensuring accurate license counts for all connectors, including those without an IP address.
Affected Users: Administrators
In AWS connectors, the default authentication method during connector setup is set to role-based authentication.
What Changed
In AWS connectors, IAM user authentication was the default method for all AWS connectors, requiring users to switch to role-based authentication if needed manually. Now, role-based authentication is applied automatically as the default, while IAM user authentication remains available as an alternative option that must be explicitly selected. This change streamlines connector setup and enhances security.
Affected Users: Administrators
In RDBMS connectors, profiling regex now manages profile status at the column level.
What Changed
In RDBMS connectors, the profiling regex did not manage profile status at the column level. When a table was included and specific columns were excluded, the excluded columns were still profiled. Now, profiling regex respects both table and column-level configurations, and only the intended columns are processed. This ensures profiling behaves as expected and improves the accuracy of metadata extraction.
Affected Users: Administrators
In Connectors, temporary lineage connectors must not appear on the connector page after lineage build.
What Changed
In connectors, temporary lineage connectors generated during a lineage build appeared on the connector page, which could cause confusion between temporary and actual connectors. Now, these temporary connectors are hidden, ensuring that only actual connectors are displayed and providing a more precise and accurate view of connector information.
Note: This change only affects the display of temporary connectors. Lineage results and connector configurations remain unchanged.
Affected Users: Administrators
In AKV Managed Identity - User Assigned, the label “Tenant” was displayed instead of “Tenant ID.”
What Changed
In connectors, the label for the tenant field was displayed as “Tenant” when creating an Azure Key Vault connection with Managed Identity – User Assigned, which could confuse. Now, the label has been updated to “Tenant Id,” aligning with standard field naming conventions and improving consistency in the connector setup interface.
Affected Users: Administrators
In the SharePoint connector, all previously disabled functions are now fully supported.
What Changed
In the SharePoint connector, several SharePoint functions were disabled due to incomplete development. The UI displayed options for authentication, cataloging, profiling, and uploading, but these features were not functional. The following capabilities are now fully supported:
- Authentication Options: On-Prem Basic and On-Prem Kerberos authentication methods are enabled.
- Version Selection: SharePoint version selection has been restored.
- File Manager Actions: Cataloging and uploading are available through the 9 Dots menu.
- Data Catalog Actions: Subfolder and file cataloging, as well as profiling, are re-enabled.
- Security Controls: Only authorized users can perform these actions.
Affected Users: All Users
In the MySQL connector, Azure Entra authentication is now supported in addition to basic authentication.
What Changed
In the MySQL connector, only basic username/password authentication, requiring manual entry of credentials for database crawling and ETL report generation, was supported. Now, the connector provides two authentication options:
- Basic Username/Password Authentication
- Azure Entra ID Authentication (when selected, the Password field is hidden)
This enhancement enables secure connections using Azure Entra authentication for database crawling and ETL report generation, reducing reliance on manual credential entry.
Affected Users: Administrators
In Connectors, the Gudu Parser now provides independent SQL parsing capabilities outside of lineage processing.
What Changed
In connectors, the Gudu Parser could parse SQL only as part of lineage processing, limiting its usability for other modules. Now, SQL statements can be parsed independently of lineage, allowing other modules to consume the parsing functionality directly. This enhancement improves modularity, reusability, and consistency of SQL parsing across the platform.
Affected Users: Administrators
In the Sisense connector, report curation is now implemented for subreports and dashboards.
What Changed
In the Sisense connector, subreports and dashboards did not fully reflect curated fields due to limitations in the reporting architecture. Now, the connector uses the updated reporting architecture, copying all columns from subreports into dashboards and transferring curation metadata. This ensures that curated fields are accurately and consistently reflected across subreports and dashboards.
Affected Users: All Users
In the Bridge Client, system statistics are now displayed for resource monitoring.
What Changed
The Bridge Client did not display system statistics, making it challenging to monitor CPU, memory, and other resource usage. Now, the client captures key metrics and presents them in a dedicated window, providing improved visibility into system performance and enabling easier monitoring and troubleshooting.
Affected Users: Administrators
REST API Connectors > Introduce Proxy attribute in connector settings.
What Changed
In the REST API connector, a proxy attribute is now available in the connector settings. When enabled, the connector uses the global Proxy configuration for all API calls. When disabled, the connector bypasses the Proxy and connects directly. This update enforces consistent proxy handling across REST API connectors, improving security and manageability.
Affected Users: Administrators
Manage Bridge Button > Restrict activation to OE_Admin role.
What Changed
The Manage Bridge button was active for users with the Connector Creator role, allowing non-admin users to access Bridge management functions. Now, the button is enabled only for OE_Admin users, while users with the Author role (non-admin) see the button disabled. This change ensures that only administrators can perform Bridge management tasks, improving control and security.
Affected Users: Administrators
In the Snowflake connector, all scheduled crawling service account jobs are halted if the connection health check fails.
What Changed
In the Snowflake connector, scheduled crawling service account advanced jobs continued to run even when the connection health check failed, which could lead to errors or inconsistent data. Now, if a connection health check fails, all scheduled jobs are halted, and a warning message is displayed for any job already running. This prevents jobs from executing on unhealthy connections and improves overall system stability.
Affected Users: Administrators
In the Data tab, the error encountered while checking sample data has been resolved.
What Changed
Running generic queries to check sample data could return very large volumes of data, causing errors and potential failures. Now, a code fix has been implemented to prevent these errors. Users are advised to run more specific queries with partition columns and date filters to retrieve the required information safely.
Affected Users: Administrators
In Azure Key Vault connectors, Managed Identity authentication is now supported.
What Changed
In Azure Key Vault connectors, only Azure Service Principal authentication was supported, requiring explicit credentials to connect and access secrets. Now, Azure Managed Identity can be used, allowing connectors to authenticate securely without providing explicit credentials. This simplifies setup, reduces manual credential management, and enhances security by leveraging Azure AD–based authentication.
Affected Users: Administrators
In File Connectors, the connector page now displays accurate counts for folders, files, and file columns.
What Changed
In File Connectors, clicking the eye icon beside a connector displayed incorrect counts: the file folder count always showed “1” regardless of the actual number of folders, the file count included both files and folders, and the file columns count did not match the cataloged data. Now, these issues have been resolved, and the connector page correctly reflects the counts for file folders, files, and file columns, improving visibility and tracking.
Affected Users: Administrators & Authors
In BridgeVM, encryption and decryption key management have been enhanced for secure storage and reuse.
What Changed
The OEDBCP processor handled encryption keys on the Bridge Client side without a dedicated mechanism for secure storage or key reuse. Now, a dedicated OEEncryptDecrypt processor manages the encryption key securely: it is transmitted once, stored on BridgeVM, and reused for subsequent requests. If the key changes in the application, it is securely updated and synchronized, ensuring consistent and secure key handling.
Affected Users: Administrators
In the OneDrive connector, the Delete Connector action no longer displays the schema page for file-based connectors.
What Changed
In the OneDrive connector, clicking Delete Connector from the 9-dots menu for file-based connectors displayed the schema page, which is not applicable because these connectors do not contain tables or schemas. Now, the schema option has been removed, and clicking Delete Connector correctly bypasses the schema page. This improves UI accuracy and prevents confusion during connector deletion.
Affected Users: Administrators
In Data Profiling, the default profiling timeout has been increased from 60 to 180 seconds.
What Changed
Profiling jobs had a default timeout of 60 seconds, which caused failures for larger datasets, complex schemas, or high-latency data sources. Now, the default timeout is increased to 180 seconds, allowing profiling jobs to complete successfully, reducing job failures, and improving the reliability of metadata extraction for broader and more complex datasets.
Affected Users: Administrators

PreviousAdvanced Tools NextAdministration

Last updated 2 months ago

Was this helpful?