Guides → Upgrade

2024.1.3

Considerations for MySQL 8.0

Before upgrading clusters that use a MySQL 8.0 metadata database from a 6.0.x or earlier release to 2024.1.x or 2024.7.1, execute the following against the Incorta metadata database:

Copy
ALTER TABLE `NOTIFICATION` MODIFY COLUMN `EXPIRATION_DATE` TIMESTAMP NULL DEFAULT NULL;

UPDATE `NOTIFICATION` SET `EXPIRATION_DATE` = NULL WHERE CAST(`EXPIRATION_DATE` AS CHAR(19)) = '0000-00-00 00:00:00';
COMMIT;

Installation process updates

Starting with the 2024.1.3 On-Premises release, to install or upgrade Incorta by directly invoking the incorta-installer.jar file, you must use the -Djdk.util.zip.disableZip64ExtraFieldValidation=true argument.

Example: java -Djdk.util.zip.disableZip64ExtraFieldValidation=true -jar incorta-installer.jar -i console

Spark 3.x

Spark 3.x requires a tmp directory with read, write, and execute permissions. You need also to specify this directory in the CMC and the spark-env.sh file.

1. Create a new tmp directory with the required permissions or use the <InstallationPath>/IncortaNode/spark/tmp directory.
2. Add the following configurations to this file <InstallationPath>/IncortaNode/spark/conf/spark-env.sh:

   Copy
   SPARK_WORKER_OPTS="-Djava.io.tmpdir=<DirWithPremissions>"
   SPARK_LOCAL_DIRS=<DirWithPremissions>
   
   

3. In the CMC > Server Configurations > Spark Integration > Extra options for Materialized views and notebooks, add the following options:

   Copy
   spark.driver.extraJavaOptions=-Djava.io.tmpdir=<DirWithPremissions>;spark.executor.extraJavaOptions=-Djava.io.tmpdir=<DirWithPremissions>
   
   

4. In the CMC > Server Configurations > Spark Integration > SQL App extra options, add the following options:

   Copy
   spark.driver.extraJavaOptions=-Djava.io.tmpdir=<DirWithPremissions> -Dorg.xerial.snappy.tempdir=<DirWithPremissions>;spark.executor.extraJavaOptions=-Djava.io.tmpdir=<DirWithPremissions> -Dorg.xerial.snappy.tempdir=<DirWithPremissions>
   
   

Next-generation loader

With the introduction of the new-generation loader, Incorta automatically detects inter-object dependencies within a load plan during the Planning phase of a load job. The Loader Service utilizes these detected dependencies and the user-defined load order within the schema to create an execution plan for loading objects. However, it’s important to note that using both the MVs' user-defined load order and automatically detected dependencies may result in an execution plan with cyclic dependencies, leading to load job failures. To avoid such failures, it is recommended to delete the MVs' user-defined load order before upgrading from a release before 6.0.

Connectors Marketplace

Starting 2024.1.3 On-Premises release, Incorta has introduced the Connectors Marketplace, allowing administrators to install, upgrade, and downgrade connectors independently from any Incorta release.

• After upgrading to 2024.1.3, the connectors’ files must be placed under the /marketplace/connectors/ directory. If this directory does not exist, create it under the system tenant path, which may vary according to Incorta installation. Afterward, you must unzip the ext_connectors.zip file that exists in the Incorta installation package and copy all the connectors’ folders from the unzipped directory to /marketplace/connectors/.
• Incorta moved the custom CData connectors from <IncortaNode>/extensions/connectors/customCData/ to <IncortaNode>/extensions/connectors/shared-libs/.
• For custom SQL connectors, you must move your custom SQL JDBC driver jars from <IncortaNode>/runtime/lib/ to <IncortaNode>/extensions/connectors/shared-libs/. In case of using a Data Agent, you must also copy these jars to incorta.dataagent/extensions/connectors/shared-libs/ on the Data Agent host.
• In case you need additional jars to use with the Oracle connector to support advanced options like XML, you must add or move the necessary libraries from <IncortaNode>/runtime/lib/ to <IncortaNode>/extensions/connectors/shared-libs/sql-oracle/.

Considerations for the MySQL driver

Starting 2024.1.3, the MySQL driver will no longer be included in the Incorta installation package or the Data Agent package. You must provide your own MySQL driver.

• For details about how to deploy your MySQL driver for Incorta installations, refer to Guides → Install MySQL Driver.
• For details about how to deploy your MySQL driver for Data Agent installations, refer to Tools → Data Agent.

Metadata database check

Upgrading to the Latest releases requires upgrading the metadata database to support multi-group load plans and migrate existing schema load jobs or load plans. Before upgrading to 2024.1.x or 2024.7.x, contact Incorta Support to perform a database check to inspect and detect any issues with your metadata database that might cause the metadata database upgrade to fail. If issues are detected, Incorta Support will run scripts against the metadata database to delete the records causing these issues.

SAP connector JCo files

Starting 2024.1.3, the SAP ERP Connector will stop bundling the JCo 3 libraries. For more information, refer to License Terms for SAP Connectors. Accordingly, you must manually get the needed libraries from SAP Java Connector and place them under <INCORTA_HOME>/IncortaNode/extensions/connectors/shared-libs/sapjco3.

Public API v2

The response of the /schema/{schemaName}/list endpoint has been updated. Some parameters have been renamed while additional parameters are now available to display error messages, the source column of runtime business view columns, and their data types. For more details, refer to Public API v2 → List Schema Objects.

Columns with Integer data type

In previous releases, Incorta wrote Integer columns in Parquet as Long. Starting 2024.1.3, Incorta writes Integer columns in Parquet as Integer for all newly created tables. For previously created tables, Incorta converts Integer columns written as Long in Parquet files to Integer during full load jobs, while Incorta keeps these columns unchanged during incremental loads.

As a result, after performing a full load of a table with Integer columns, it is recommended that you perform a full load of its dependent schema objects to ensure data consistency.

To migrate all Parquet files to have Integer data without fully loading your objects, the administrator can turn on the Enable Parquet Migration at Staging option in the Cluster Management Console (CMC) > Server Configurations > Tuning and perform a load from staging for all your objects with Integer columns.

Notes:

• Turning the Enable Parquet Migration at Staging option on adds a new step that runs on Spark to the staging load jobs. Ensure Spark has sufficient resources to migrate the required Parquet files.
• The migration of Parquet files during staging load occurs only once per object.
• Load tables before loading MVs that read from these tables.
• When loading an object fully, you must load dependent objects or load all objects from staging after turning the Enable Parquet Migration at Staging option on.
• The new behavior might affect existing scripts referencing Integer or Long data, whether columns, values, or variables.

Schema names

Starting 2024.1.3, the names of newly created physical schemas and business schemas are not case-sensitive. Therefore, you cannot create a new physical or business schema that shares the same name with existing schemas, whether physical or business, using different letter cases.

To maintain backward compatibility, the names of existing schemas and business schemas will not be affected.

Caching mechanism enhancements

The caching mechanism in Analyzer views for dashboards has been enhanced by caching all columns in the view to prevent query inconsistencies. To optimize performance and reduce off-heap memory usage, creating views with only the essential columns used in your dashboards is recommended.

Like function fix

As a result of fixing an issue with the like() function, you must load all tables that use this function from staging if you are upgrading from releases before 6.0.2.

External Notebooks

In the case of using external Notebooks, you must force reinstalling the Python library after upgrading from a release before 6.0.

SDK Component installation

For now, SDK Component installation is only supported on clusters that use a MySQL metadata database.

2024.1.4

SQLi service consideration

Starting 2024.1.4, the SQLi service must be started before creating or processing SQL views over non-optimized tables or Incorta-over-Incorta tables via Spark port; otherwise, Incorta throws an error.

2024.1.5

Single Logout for SAML2 SSO providers

Starting 2024.1.5, Incorta supports Single Logout (SLO) for SAML2 SSO identity providers, including Azure Active Directory (AD) and OneLogin. When users sign out from Incorta, they are automatically signed out from their SAML2 SSO identity providers.

The Single Logout URL on both Incorta and the identity provider must be set to Incorta’s login page URL, for example, https://myCluster.cloud.incorta.com/incorta/!myTenant/ or https://10.10.1.5:8080/incorta/!myTenant/.

In the case of OneLogin, set the SAML initiator option to Service Provider.

Update the SSO configurations on Incorta and add the following settings:

• onelogin.saml2.idp.single_logout_service.url: The logout URL provided in your SSO provider's metadata.xml
• onelogin.saml2.sp.single_logout_service.url: Incorta’s login URL, for example, https://myCluster.cloud.incorta.com/incorta/!myTenant/ or https://10.10.1.5:8080/incorta/!myTenant/
• onelogin.saml2.sp.single_logout_service.response.url: Incorta’s login URL

2024.1.7

After upgrading to 2024.1.7 and with the introduction of Incorta Premium, the following features will be impacted:

• Notebook for business users: Enable Incorta Premium to be able to access existing business notebooks and create new ones.
• Data Studio: To avail the Data Studio tab in the Analytics platform, enable Incorta Premium, enable Data Studio for Cloud clusters in the Cloud Admin Portal > Configurations, and enable and configure it in the CMC > Server Configurations > Incorta Data Studio.

2024.1.8

Caching updates

• The default value of the Maximum Cached Entries has been increased from 2,000 to 20,000. This change will not impact values manually set before the upgrade.
• A new option is available to control the maximum size of insight query results to be cached. The default is 30 MB.

Strict PostgreSQL syntax validation for materialized views

MVs containing non-compliant PostgreSQL syntax, including improper identifier quoting or case sensitivity issues, will fail validation and execution. MVs that were functioning properly in previous releases may require syntax corrections after upgrades to ensure PostgreSQL compliance.

Example: If a quoted identifier (e.g., "AMOUNT_SOLD") does not exactly match the column name as defined, including case sensitivity, the query will fail.

2024.7.1

Considerations for MySQL 8.0

Before upgrading clusters that use a MySQL 8.0 metadata database from a 6.0.x or earlier release to 2024.1.x or 2024.7.1, execute the following against the Incorta metadata database:

Copy
ALTER TABLE `NOTIFICATION` MODIFY COLUMN `EXPIRATION_DATE` TIMESTAMP NULL DEFAULT NULL;

UPDATE `NOTIFICATION` SET `EXPIRATION_DATE` = NULL WHERE CAST(`EXPIRATION_DATE` AS CHAR(19)) = '0000-00-00 00:00:00';
COMMIT;

JDK supported versions

JDK 8u144 is no longer supported, and you must upgrade to JDK 8u171 or later.

Spark 3.4.1

Starting this release, Incorta uses Spark 3.4.1. All Incorta applications, including the Advanced SQL Interface, will use one unified Spark instance (<incorta_home>/IncortaNode/spark/) to handle the different requests. For more details about the difference between the Spark versions, refer to the 3.4.1 Migration Guide.

As a result of using a unified Spark instance, you must consider the following when upgrading On-Premises clusters that have the Advanced SQLi previously enabled and configured:

• Take into consideration the resources required by the Advanced SQLi when configuring the Spark worker resources in the CMC.
• Post upgrade, make sure that the CMC is started and running before starting the services related to Advanced SQLi, such as the Advanced SQL service and Kyuubi, to have the configuration values updated to refer to the unified Spark instance instead of SparkX.

Schema load notifications

To upgrade a cluster with schema load notifications from a release before 2024.1.0 to any 2024.7.x release, upgrade to a 2024.1.x release first, and then upgrade to the required 2024.7.x release to have the schema load notifications migrated correctly to load plan notifications.

Deprecating Incorta custom Delta Lake reader

Starting this release, Incorta has deprecated its custom Delta Lake reader and started to use only Spark Delta Lake reader to read Delta Lake files.

Load jobs and scheduled plans

Before starting the upgrade process, do the following:

• For each tenant in your cluster, pause the load plan schedulers: In the Cluster Management Console (CMC) > Tenant Configurations > Data Management, turn on the Pause Load Plans toggle.
• Stop all load jobs, including in-progress and in-queue jobs: In the Schema Manager, select Load Jobs, and then select Stop for each job you want to stop.

Load filters

During the upgrade, existing load filters for a table will be migrated as partial loading filters. After the upgrade, tables with load filters will require a load from staging.

Accounting for nulls in the Loader Service

Starting 2024.7.1, Incorta Loader accounts for null values in the following contexts whether or not you enable Null Handling in the CMC:

• Deduplication and PK-index calculations:
  The Loader Service will consider null values as undefined values. Thus, null values are no longer considered zeros or empty values. When loading data in full or incremental load jobs, the Loader Service will retrieve or update records with null key values apart from records with zero or empty key values. However, to preserve backward compatibility, Incorta considers a null value equal to another null value when retrieving or updating data. Accordingly, only one record with a null value will be loaded or updated if the Enforce Primary Key Constraint option is enabled.

  
  

• Join calculations and join filters:
  The Loader Service will account for records with null values individually. During join calculations, a null value does not equal another null value, zero, or empty value. Additionally, the Loader Service will account for null values when evaluating the join filter.

Intelligent Ingest

After upgrading to 2024.7.1, previously configured incremental ingest jobs may fail or cause data inconsistencies at the destination. To prevent these issues, perform a full ingest before running the first incremental ingest post-upgrade.

Note: This requirement does not apply to schemas configured for ingestion for the first time after the upgrade as they will automatically undergo a full ingest during the initial ingest job.

Notebook for business users

Users who created business Notebooks in previous releases of Incorta will need the newly released Advanced Analyze User role for continued access in 2024.7.x.

Upgrades from 2024.1.7

A new version of the Excel Add-in has been introduced in 2024.1.7. This new version is supported in the 2024.7.x releases starting with 2024.7.4. Therefore, upgrading from 2024.1.7 to 2024.7.1, 2024.7.2, and 2024.7.3 is not recommended for the Excel Add-in users.

Upgrades from 2024.1.8

The Early Post-load calculations feature introduced in the 2024.1.8 release will not be available in any 2024.7 or 2025.7 release until further notice. We will provide updates regarding its availability in future releases.

2024.7.2

Incorta Premium

After upgrading to 2024.7.2 and with the introduction of Incorta Premium, the following features will be impacted:

• Notebook for business users: Enable Incorta Premium to be able to access existing business notebooks and create new ones.
• Spark SQL Views: To create new, explore, edit, and visualize Spark SQL Views, enable Incorta Premium and Spark SQL View in the Server Configurations > Incorta Labs.
• Data Studio: To avail the Data Studio tab in the Analytics platform, enable Incorta Premium, enable Data Studio for Cloud clusters in the Cloud Admin Portal > Configurations, and enable and configure it in the CMC > Server Configurations > Incorta Data Studio.
• Copilot: To have access to Incorta Copilot and generative AI capabilities, enable Incorta Premium, enable and configure Copilot for Cloud clusters in the Cloud Admin Portal > Configurations, and enable and configure it in the CMC > Server Configurations > Incorta Copilot.

2024.7.3

Null handling

• Null Handling is now an independent feature, separate from Advanced SQL Interface (Advanced SQLi). You can enable or disable it as needed. After upgrading to 2024.7.3, clusters with Advanced SQLi enabled will automatically have Null Handling enabled as well.
• During join calculations, the Loader Service will handle null values based on the Null Handling CMC setting.
  • Disabled: The Loader Service treats Null values as zeros for numeric columns, empty strings for text columns, and empty dates for date columns.
  • Enabled: The Loader Service treats Null values as distinct values, not equivalent to zeros, empty strings, or other null values.

Spark Metastore

You must sync the Spark Metastore after upgrading to this release to ensure access to Spark SQL views and insights leveraging them. Go to the CMC > Clusters > <cluster_name> > Tenants > <tenant_name> > More Options (⋮), and then select Sync Spark Metastore.

Clusters with Advanced SQLi

To ensure consistent null handling behavior after upgrading multi-Analytics clusters with Advanced SQLi enabled from earlier 2024.x releases to 2024.7.3, remove engine.enable.null.handling=true from all Analytics service and node property files , and then restart affected services.

2024.7.4

On-Premises clusters using MySQL

• For a smooth upgrade process for clusters with MySQL metadata database, ensure your metadata database server runs MySQL 8.0.
• Customers running Incorta On-Premises with a MySQL metadata database, where the MySQL server is configured to automatically add invisible primary keys to tables without one, should contact the Support Team for assistance in upgrading their clusters to this release.

Strict PostgreSQL syntax validation for materialized views

MVs containing non-compliant PostgreSQL syntax, including improper identifier quoting or case sensitivity issues, will fail validation and execution. MVs that were functioning properly in previous releases may require syntax corrections after upgrades to ensure PostgreSQL compliance.

Example: If a quoted identifier (e.g., "AMOUNT_SOLD") does not exactly match the column name as defined, including case sensitivity, the query will fail.

Null Handling updates

• In this release, the Incorta Engine will treat null values in numeric columns as zeros and data columns as the maximum Java date when performing arithmetic operations (+, -, *, /, %), regardless of the Null Handling setting in the CMC.

  • This change is limited exclusively to arithmetic operations and does not affect other functions, such as sum, average, addMonths, or similar calculations.
  • Formulas with decimal columns divided by null will throw an error instead of returning a null value.
  • However, when Null Handling is enabled, the Advanced SQL Interface will continue to treat null values as true nulls in arithmetic queries originating from third-party visualization tools, Spark SQL Views, and Business Notebooks.
    Important

    If Null Handling was enabled before the upgrade, you must reload schemas related to formulas containing null values with arithmetic operations from staging to ensure consistent data.

• This release has fixed the discrepancy where the null category (coloring dimension) was not displayed in charts when using numerical or date grouping dimensions while it was displayed for string grouping dimensions. After upgrading to this release, all charts with a coloring dimension that contains null values will, by default, display a null category. To hide it, apply a Not Null filter to the coloring dimension column.

Caching updates

• The default value of the Maximum Cached Entries has been increased from 2,000 to 20,000. This change will not impact values manually set before the upgrade.
• A new option is available to control the maximum size of insight query results to be cached. The default is 30 MB.

Engine Audit updates

In this release, a new version of the Enhanced Engine Audit, engine_audit.2.1, is now available with new audit files and updates to existing ones.
After upgrading, audit data will be stored in the engine_audit.2.1 folder. If you have schemas reading from the old engine_audit.2.0 folder, create multi-source tables that read from both folders to maintain a complete audit history.

Clusters on Azure

To upgrade your clusters deployed on Microsoft Azure to 2024.7.4, contact the Support Team.

2024.7.5

CentOS Linux 7.x Deprecation

Starting with 2024.7.5, support for the CentOS Linux 7.x operating system is officially discontinued. Customers currently running Incorta on CentOS Linux 7.x must upgrade their underlying operating system to a supported version before upgrading to Incorta 2024.7.5.

Installation process updates

Starting with this release, the installation process for Incorta will run exclusively in console mode when using the install script, and the GUI mode will no longer be available. Just run ./install to start the installation or upgrade process.

Clusters with Copilot-Slack integration

Please contact the Support team to plan for upgrading your 2024.7.4 cluster if it has active integration between Incorta Copilot and Slack.

Lineage information availability

Due to processing dependency calculations in the background apart from the Engine startup, lineage information may be temporarily unavailable if requested immediately after the Analytics Engine startup. In such cases, a message will be displayed indicating that lineage details are not yet accessible.

2024.7.6

Supported Java versions

This release exclusively supports OpenJDK 17. It is required to install or upgrade to the supported Java version before installing or upgrading to the 2024.7.6 release.

Adopting OpenJDK 17 is anticipated to deliver substantial improvements in both performance and stability for your Incorta platform, ensuring a more robust and efficient experience.

Behavior changes

IN operator with only -1 in filters

Previously, when the IN operator was used with only -1 in any of the following filter types, the system returned all data instead of only records with the value -1.

• Insight Filters
• Applied Filters
• Filter Options

After the upgrade, using IN (-1) in these filters works as expected and correctly returns only records where the value is -1.

Load plan permissions

Users with Edit access to all physical schemas in a load plan can now edit or suspend it. Previously, only load plan owners and Super Users had this capability.

Service configuration restrictions

Starting with this release, Cloud administrators can no longer edit the service's memory configurations within the Cluster Management Console (CMC). This change centralizes memory management, ensuring that all service configurations adhere to optimized cloud deployment standards.

2024.7.7

Behavior changes

Null values in KPIs

Starting with this release, KPI insights now honor the Null Value Representation setting configured in the CMC > Tenant Configurations > Customizations, ensuring consistent handling of null values in KPI and tabular insights.

Stricter permissions for single insight delivery

Users must now have at least Share access to a dashboard and the appropriate roles to send or schedule the delivery of single dashboard insights via email or send them to data destinations. Those without the required access can no longer perform these actions, aligning insight-level permissions with the existing rules that govern dashboard sharing and delivery.

2025.7.1

Installation and upgrade requirements and recommendations

Deprecating support for Oracle 12c

Starting with this release, the Oracle 12c database server is no longer supported for the Incorta metadata database. Customers who are still using Oracle 12c for their metadata should upgrade to Oracle 19c.

Please contact Incorta support for any questions regarding this.

Supported Java versions

This release exclusively supports OpenJDK 17. It is mandatory to install or upgrade to the supported Java version before installing or upgrading to the 2025.7.1 release.

Adopting OpenJDK 17 is anticipated to deliver substantial improvements in both performance and stability for your Incorta platform, ensuring a more robust and efficient experience.

Supported Python versions

Although Python 3.8 and 3.9 are still supported, it is strongly recommended to use Python 3.10.12. Adopting the recommended version will allow you to leverage the latest security enhancements and critical fixes, ensuring a more secure and stable environment.

Connectors

After upgrading to Incorta 2025.7.1, it is mandatory to upgrade all CData and Presto connectors to their latest versions for continued functionality. Additionally, it is recommended to upgrade all other connectors to benefit from the recent fixes and enhancements.

Perform these upgrades using the Connector Marketplace.

New user interface

The 2025.7.1 release introduces a redesigned and modernized user interface (UI) for an improved user experience. Please note that reverting to the previous UI is not supported in this release.

Existing custom style sheets (CSS) you have implemented will be outdated after the upgrade and will require updates to align with the new UI's structure.

For details about the new selectors and necessary updates to your custom CSS, refer to References → Customize Incorta with CSS.

Incorta Copilot is now Incorta Nexus

With this release, Incorta Copilot has been renamed to Incorta Nexus. The new name better reflects its expanded role in delivering intelligent, context-aware analytics and advanced data interactions across the platform.

Clusters with Advanced SQLi

For On-Premises, Multi-Analytics clusters with Advanced SQLi enabled, the manually configured primary Analytics service must be removed. To ensure proper operation, you must reconfigure the primary Analytics service after the upgrade from the CMC.

In custom installations, with single-Analytics or multi-Analytics environments, you must explicitly configure both the Analytics node and service for Advanced SQLi; otherwise, Spark Metastore Sync will fail to initialize.

For details, see Streamlining the primary Analytics configuration.

Stricter schema import validation

Incorta releases prior to 2024.1.0 allowed the creation of physical or business schemas with identical names that only differed in capitalization. While version 2024.1.0 restricted the creation of such schemas, this limitation did not apply to schema imports.

In releases starting 2025.7.1 through 2025.7.5, Incorta enforced this naming convention during physical and business schema imports, preventing the import of physical or business schemas whose names are duplicates of existing ones (whether physical or business) but differ in capitalization.

IN operator with only -1 in filters

Previously, when the IN operator was used with only -1 in any of the following filter types, the system returned all data instead of only records with the value -1.

• Insight Filters
• Applied Filters
• Filter Options

After the upgrade, using IN (-1) in these filters works as expected and correctly returns only records where the value is -1.

getVar function behavior change

In this release, the behavior of the getVar function in Spark SQL views has been updated. If the referenced variable returns multiple values, getVar will now return them as a single, comma-separated string, instead of returning only the first value as in previous versions.

This may affect existing views that rely on the previous behavior. Please review and update any impacted queries accordingly.

Analyzer tables on secured base tables

Previously, the $user system variable in the source object’s security filters would be evaluated incorrectly when loading or exploring Analyzer tables based on this object, leading to empty or inaccurate result sets.
Starting with this release, any security filter in the base object containing $user will be ignored when loading or exploring the dependent Analyzer table.

For details, see Analyzer tables based on objects with security filters.

Upgrades from 2024.1.8

The Early Post-load calculations feature introduced in the 2024.1.8 release is unavailable through all later 2024.x and 2025.x releases. The feature has only become available again starting with release 2026.3.0

Service status observability port review

After upgrading to this release, it's critical to review and verify that the status observability ports are available and accessible by Incorta. This review should be conducted before starting the services to ensure proper service startup and status reporting.

The default ports are:

• 65531 for the Analysis service
• 65532 for the Loader service

In the case of a multi-Analytics node, you must manually change the status observability port for one of the Analytics services in the service.properties file. For more details refer to Service status observability.

Service configuration restrictions

Starting with this release, Cloud administrators can no longer edit the service's memory configurations within the Cluster Management Console (CMC). This change centralizes memory management and ensures that all service configurations adhere to optimized cloud deployment standards.

Date and cluster name added to the audit file name

The naming convention of the Engine audit files has been changed.

• Old pattern: <nodeName>.<serviceName>-part<partNumber>.csv
  Example: c71-node.analytics-part-00000-00.csv
• New pattern: <date>-<clusterName>.<nodeName>.<serviceName>-part<partNo.>.csv
  Example: 2025-05-15-c71.c71-node.analytics-part-00000-00.csv

2025.7.1 Data agent considerations

• This release uses the Data Agent version 12.0.1. Please upgrade to this version.
• For Cloud clusters, data agents are now managed from the Cloud Admin Portal and not the Data Manager.
• After upgrading the data agent, do the following:
  • Regenerate the authentication file from the Cloud Admin Portal and copy it to the following directories on the remote host machine:
    • <unzipped_data_agent_path>/incorta.dataagent/conf
    • <unzipped_data_agent_path>/incorta.dataagent.controller/conf
  • Ensure that you whitelist the public host and port used by the controller to connect to the CMC service (the default port on a Cloud cluster is 6260), along with the public hosts and ports of the Analytics and Loader services used by the data agent to connect to these services.
    • To get the public hosts and ports of the Incorta services on a Cloud cluster, do one of the following:
      • In the Cloud Admin Portal, connect your Cloud cluster, select the Advanced Configurations tab, select Server Configurations, and then select Data Agent.
      • In CMC, navigate to Clusters > <yourCluster> > Cluster Configurations > Server Configurations > Data Agent.
    • Ensure that you whitelist port 6261 as well to prepare for automatic data agent upgrades during Incorta Cloud cluster updates.
• Enhanced memory management options are now available for the data agent.
  • The data.agent.fetch.size property in the node.properties file has been deprecated. Any configured value will be ignored after upgrading to this release.
  • The data source fetch size must not exceed the estimatedFetchSize configured for the corresponding data agent to avoid out-of-memory errors while fetching data.

For details, see Data agent memory management.

2025.7.2

Single Logout with ADFS identity provider

Starting with the 2025.7.2 release, SAML Single Logout (SLO) is enforced. When using Microsoft Active Directory Federation Service (ADFS) as the identity provider, you must ensure the following configurations are in place to guarantee proper logout behavior:

• NameID is present in the login response.
• All logout messages are signed.
• ADFS trusts the service provider (SP) signing certificate. Contact the Incorta Support team for the SP signing certificate.

Failure to complete these mandatory configurations will cause the SAML logout process to fail.

2025.7.2 Data Agent supported version

This release uses the Data Agent version 12.0.1.

• Customers upgrading from a release before 2025.7.1 must follow the steps mentioned in 2025.7.1.
• For upgrades from 2025.7.1, no action is required as the 2025.7.2 release uses the same Data Agent version as 2025.7.1.

2025.7.3

2025.7.3 Data Agent considerations

This release uses the Data Agent version 12.0.2. Please upgrade to this version.

• Customers upgrading from a release before 2025.7 must follow the steps mentioned in 2025.7.1.
• Customers upgrading from a 2025.7.x release:
  • For Incorta Cloud clusters: No action is required. The data agent will be upgraded automatically during the cluster upgrade, provided that the 6261 port is whitelisted before the cluster upgrade.
  • For other deployments (On-Premises and customer Cloud clusters): Upgrade the data agent manually as mentioned in the 2025.7.1 release notes.
• The Data Agent Memory Manager is disabled by default in this release.

2025.7.4

Data agent considerations

This release uses the Data Agent version 12.0.3.

The data agent upgrade considerations of release 2025.7.3 still apply to this release. However, this data agent version fixes critical issues that have affected 2025.7.x releases.

Conditional formatting based on another field

In earlier 2024 and 2025 releases, conditional formatting based on a different field produced inconsistent results in Excel exports, sometimes applying incorrect styles that did not match the dashboard view.
Starting this release, Incorta will disregard conditional formatting when exporting to Excel to maintain data integrity and avoid misleading visual cues.

Null values in KPIs

KPI insights now honor the Null Value Representation setting configured in the CMC > Tenant Configurations > Customizations, ensuring consistent handling of null values in KPI and tabular insights.

Stricter permissions for single insight delivery

Users must now have at least Share access to a dashboard and the appropriate roles to send or schedule the delivery of single dashboard insights via email or send them to data destinations. Those without the required access can no longer perform these actions, aligning insight-level permissions with the existing rules governing dashboard sharing and delivery.

2025.7.5

Data agent considerations

This release uses the Data Agent version 12.0.3; the same version supported for 2025.7.4. Accordingly, the data agent upgrade considerations of release 2025.7.3 continue to apply to this release.

2026.3.0

Data agent considerations

This release uses the Data Agent version 13.0.5. The data agent upgrade considerations of release 2025.7.3 still apply to this release.

MongoDB BI Connector compatibility with MySQL Connector/J 9.4.0

Starting with this release, Incorta Cloud uses MySQL Connector/J 9.4.0 JDBC driver (instead of MySQL Connector/J 5.1.48), which enforces CLIENT_PLUGIN_AUTH during the authentication handshake. Older versions of the MongoDB BI Connector do not support this capability, causing the connection to fail with an authentication error.

After upgrading to 2026.3.0 or later, your MongoDB data source connections may fail if your MongoDB BI Connector version is not compatible with the updated JDBC driver.

Before upgrading, take one of the following actions:

• Upgrade your MongoDB BI Connector to a version that supports the CLIENT_PLUGIN_AUTH capability required by MySQL Connector/J 9.4.0.
• If upgrading the MongoDB BI Connector is not possible, contact the Support team to downgrade the JDBC driver to a compatible version.

For On-Premises and customer-managed cloud installations, ensure that the MySQL Connector/J driver added to the <IncortaNode>/extensions/connectors/shared-libs/ directory is compatible with your MongoDB BI Connector version.

Behavior changes

Data Profiler schema availability update

The Data Profiler schema is no longer provided through the Data Quality Data App. Contact your Account Executive to configure the Data Profiler schema.

Dynamic Group By support for scheduled dashboard exports

Scheduled dashboard exports in Excel and CSV formats now apply the selected or default Dynamic Group By configuration for each insight, ensuring that exported data reflects the intended grouping defined for the dashboard.

Null values in KPIs

Starting with this release, KPI insights now honor the Null Value Representation setting configured in the CMC > Tenant Configurations > Customizations, ensuring consistent handling of null values in KPI and tabular insights.

A change in the schema settings

The Performance Optimization option in the schema Settings and More Options menus has been removed starting with this release. You can continue to manage in-memory data behavior at the table level through each table’s Advanced Settings > Loaded Data in Memory, which provides more control over memory-loading options.

Post-load calculation as part of the Running phase

Post-load calculations are no longer handled as a separate stage and are now included within the Running phase. You can review the Running phase breakdown, including Extraction, Deduplication, Load, and Post-load, in the Load Job Details Viewer.

Stricter permissions for single insight delivery

Users must now have at least Share access to a dashboard and the appropriate roles to send or schedule the delivery of single dashboard insights via email or send them to data destinations. Those lacking the required access can no longer perform these actions, aligning insight-level permissions with the existing rules that govern dashboard sharing and delivery.

Data Studio Data Quality Rules enhancement

Data quality rules are now managed in metadata rather than CSV files, with automatic migration, improved export and import support, and enhanced accuracy and governance.

v8.0.0 - 2026.8

Supported Java versions

This release exclusively supports OpenJDK 21. It is mandatory to install or upgrade to the supported Java version before installing or upgrading to the v8.0.0 - 2026.8 release.

Adopting OpenJDK 21 brings improved garbage collection performance, reduced memory overhead through virtual threads, and enhanced security with the latest cryptographic standards. Java 21 is also the runtime required by Spark 4, ensuring full compatibility across all upgraded components in this release.

GCS connector and Hadoop upgrade

The Google Cloud Storage (GCS) connector has been upgraded to version 3.0.11 and Hadoop to version 3.4.1.

On-Premises GCS installation

For On-Premises clusters with GCS storage, add the following property to the core-site.xml, then run the Python scripts to propagate the updated file to all required locations:

Copy
<property>
  <name>fs.gs.auth.type</name>
  <value>APPLICATION_DEFAULT</value>
</property>

Enhanced security by bundling Apache Tomcat v11.0.22

In this release, Incorta bundles Apache Tomcat 11.0.22 to catch up with the security enhancements and fixes in this version, ensuring a more secure and up-to-date runtime environment.

Runtime component upgrades

This release upgrades the following underlying runtime components:

Most customers can upgrade without changes. Customers using custom code, external JARs, or external Python packages should review the compatibility notes below.

Spark 4 and Python 3.12

This release upgrades Incorta to Spark 4 and Python 3.12, delivering faster performance, broader SQL compatibility, and updated ecosystem libraries.

Before upgrading, it is recommended to run the Spark 4 / Python 3.12 issue detection tool, issue-detector.sh, to check scripts of materialized views, MV-level Spark properties, and cluster-wide Spark configuration. Resolve all reported issues before proceeding, and contact Incorta Support for upgrade assistance.

The detection tool performs static analysis only and will not catch all runtime issues. Reported findings are potential concerns, not guaranteed failures.

PySpark compatibility

PySpark Materialized Views and notebooks may require updates for Python 3.12. Verify that any external Python packages you use support Python 3.12, including:

• Pandas 2.0.0 or later
• NumPy 1.21 or later

SparkR deprecation

SparkR is deprecated and will be removed in a future release. It remains supported for materialized views and notebooks in this release, but customers are encouraged to migrate SparkR workloads to Scala or PySpark now to simplify future upgrades.

JDK 21 and Scala 2.13

Scala Materialized Views should be compatible with Scala 2.13 and JDK 21. If your MVs or Spark applications reference external JARs, ensure those libraries also support the JDK 21 runtime before upgrading.

Cloud deployments: external Spark artifacts

For Cloud deployments, review any external Spark artifacts added through the Cloud Console, including Python packages and custom JARs, to ensure they are compatible with the updated Java (21), Scala (2.13), Spark (4.0.2), and Python (3.12.3) runtimes before upgrading.

ANSI SQL mode for Spark

Spark 4 enables ANSI SQL mode by default. To maintain compatibility with existing Incorta materialized views and notebooks, Incorta keeps ANSI SQL mode disabled by default in this release.

To enable it, navigate to CMC > Server Configurations > Spark Integration, and turn on the Enable ANSI SQL for Spark Applications toggle.

Enabling ANSI SQL mode is recommended for standards compliance. However, as it changes the behavior of certain SQL operations, particularly around null handling and error reporting, validate your existing materialized views before enabling it in production.

Parquet Libraries 1.15.2

The Parquet library has been upgraded from version 1.12.2 to 1.15.2. This upgrade delivers security fixes, improved ecosystem stability, and enhanced performance for Parquet read/write operations.

Databricks data destination

The Send to Destination feature for Databricks now requires Unity Catalog (UC) Volume access when using an existing Databricks schema or table. Additionally, the option to configure the Incorta tenant directory path directly from the data destination UI has been removed.

For more details, see Cloud-agnostic Databricks destination.

Data Governance considerations

This release requires updates to both the Data Quality and Data Catalog packages. Existing installations must re-import the schemas and re-run the relevant load plans to ensure accurate results.

Before importing, ensure that the Data Quality and Data Catalog load plans, and any other load plan that uses these schemas, are not running, so the schemas can be imported successfully with Overwrite enabled.

The Term ID column has moved from the dg_dq_rule table to the new dg_dq_rule_term table, both in the _incortaGovernanceMetadata schema. Re-importing the schemas below updates this automatically. If you have custom reports or queries referencing this column, point them to the new table.

Data Quality considerations

The Data Quality package is updated in this release. To ensure quality scores are calculated properly for terms and columns, the Data Quality schemas must be updated. Complete these steps:

1. Download and extract the Data Quality Package

2. Navigate to Schema > Import.

3. Select schemas.zip from the extracted data-quality-blueprints folder and enable Overwrite.

4. Navigate to Scheduler > Load Plan > Import Load Plan.

5. Run the Data Quality Load Plan.

   For more information, refer to the Data Quality Package Installation and Configuration Guide.

Data Catalog considerations

The previous Catalog Overview Assets package is no longer compatible. To ensure accurate report results, the Data Catalog schemas must be updated. Complete these steps:

1. Download and extract the Data Catalog Package

2. Navigate to Schema > Import.

3. Select schemas.zip from the extracted data-catalog-blueprints folder and enable Overwrite.

4. Run the Data Catalog Load Plan.

   For more information, refer to the Data Catalog Package Installation and Configuration Guide.

Data Masking considerations

Any Data Classification entry in the Data Catalog with the Data Masked toggle enabled is automatically migrated, along with its exception groups, to the new Data Masking tab under Data Governance.

• Migrated rules follow the naming format: _Migrated_<ClassificationName>
• The rule description includes the full path of the associated terms

This applies to both upgrades and Data Catalog imports from any environment running a version prior to v8.0.0 - 2026.8.

SQLi considerations

Masking rules that were previously not applied to SQLi queries are now enforced. After upgrading, existing reports and integrations may return masked values. Review your masking rules and role assignments before upgrading to ensure they produce the expected results.

Data agent upgrade considerations: Java 21 required

This release ships Data Agent 16.1.1. which requires Java 21 (OpenJDK 21.x or Oracle JDK 21.x). Before upgrading, verify Java 21 is installed, and JAVA_HOME points to it on every machine running the data agent. Upgrading or starting the data agent on a machine running an older Java version will fail.

The Data Agent version 16.1.1 provides multiple enhancements.

Behavior changes

Streamlined file upload in the Data Manager

The Upload Data Files and Upload Data Folder options are now available directly from the + New button in the Data tab. Previously, you could access these actions through the Add New Data Source flow, which required additional steps for a common task. As a result, the Data Files section has been removed from the Choose a Data Source dialog.

SQLi and PostgreSQL views

In SQLi and PostgreSQL views, the expression NULL IS NULL was incorrectly evaluated as FALSE instead of TRUE. This could occur when the expression was written explicitly in a query, or when it resulted from internal query translation. In such cases, affected queries or filters could unexpectedly return no data. This release fixes this issue. Thus, after upgrading, results for such queries may differ; previously missing rows will now be correctly returned.

CMC concurrent sessions

The Cluster Management Console (CMC) previously allowed unlimited simultaneous logins per user. This release introduces a new internal configuration to limit concurrent sessions per user with a default setting of 10 sessions. When exceeding this limit, the system automatically invalidates the oldest session. You can change the default setting by adding the cmc.maximum.concurrent.sessions property to cmc.cfg. Restart the CMC after changing this setting.

Insight hover behavior

Hovering over an insight no longer displays a border or the context menu icon, reducing visual clutter. Select More Options (⋮) to access the context menu.

Connectors Marketplace

The Select a Version drop-down list in the Connector Marketplace now displays connector versions in descending order, with the latest version at the top. By default, the list shows the 30 most recent versions, making it easier to find and select a specific version without scrolling through the full version history.

Incorta Swagger REST Public API page

• You need to add your token, personal access token or OAuth 2.0 JWT, via the new global Authorize option, not the per-endpoint Authorization header field.
  • Note: Swagger UI won't let you leave that per-endpoint field empty, so you'll need to enter a placeholder value there.
• You no longer need to select a scheme (HTTP or HTTPS) before using the Incorta Swagger REST Public API page. The page now handles scheme selection automatically.
• The Swagger JSON URL has changed from https://<CLUSTER_URL>/incorta/api/v2/swagger.json to https://<CLUSTER_URL>/incorta/api/v2/openapi.json.
  • Important: Update any existing integrations, scripts, or bookmarks that reference the previous swagger.json URL directly, as they will no longer resolve after the upgrade.