You are viewing content for 4.7 | 4.6 | 4.5 | 4.4 | 4.3 | Previous Releases

Release Notes 4.3

Welcome to the latest features, enhancements, and main fixes in version 4.3.

Maintenance Pack Announcements for Release 4.3

Incorta delivers maintenance packs with bug fixes to update major and minor releases.

The following maintenance packs were issued for Incorta Analytics Release 4.3.

Maintenance Pack 11 (November 13, 2019)

  • Dashboards & Insights. Fixed an issue where dashboards were not rendering data after a schema load. This is attributed to schema updates that were being made while the analytics service was still updating the joins for all the incremental records from the load that has just completed.
  • Dashboards & Insights. Resolved an issue where the dashboard was still displaying old values after an incremental
  • Dashboards & Insights. Resolved an issue that was displaying the wrong date in the date picker selection. Removed browser timezone dependency for date/time formatter.
  • Dashboards & Insights. Fixed a bug that gave an error message ‘required column not loaded into memory’ on the dashboard. load had finished.
  • Loader Service. Resolved an issue that was preventing a job from being archived.
  • Loader Service. Fixed a bug that was failing to ‘materialize table’ when loading an Incorta table.
  • Loader Service. Resolved an issue that was giving an error when trying to simultaneously load parent and child table on two different loader nodes.
  • Loader Service. Resolved an issue that was failing schema full load.
  • Loader Service. Enhancement to clear the row set off-heap memory after an incremental load.
  • Log Files. Fixed a typo that displayed in an analytics error log file for data type mismatch issues: “Column type does match.” The error log now says, “Column type does not match.”
  • Schemas. In an Incorta table, a materialized query in the physical schema may need to be manually loaded or refreshed after a schema load. This may be required if this Incorta table has a dependency across two or more schemas and these schemas are being loaded concurrently.
  • Schemas. Disabled schema deletion while schema is loading.
  • Schemas. Disabled schema editing while schema is loading from the system backend.
  • SQL Interface. In prior versions of Release 4.3.10 and before, the spark driver would return SQL-Interface based Spark SQL query result sets concurrently, leading to out of memory errors. Implemented a throttling mechanism to serialize the result set and minimize the SQL App failing and restarting.
  • SQL Interface. Fixed the issues that were resulting in large memory consumption and memory leakage on the analytics services when querying large result sets. Moved the JDBC protocol message handling to the Spark side, so that the analytics service merely serves as a conduit between the spark server and the JDBC client.
  • SQL Interface. Enhanced the SQL App logic to clear data frame and release the memory, if the client closes the result-set, or if it crashed or disconnected during the process of serving the result set.
  • SQL Interface. Resolved an issue that was giving an error when trying to do a schema discovery from PowerBI.
  • Tables. Fixed a bug that was preventing Incorta table creation.

Maintenance Pack 10 (August 27, 2019)

  • Loader. Fixed an issue with loading Incorta tables when two schemas with dependencies were loaded at the same time. The dependent schema was not locked until the parent schema load was complete.
  • Loader. Enhanced logging where writing snapshot for tables will also include table joins.

Maintenance Pack 9 (August 8, 2019)

  • Charts. Converting Charts To Tables Yields Different Values
  • Front-End Web. Backport - Table Aliases need to refresh automatically on base table changes
  • Loader. Unable to load a schema
  • Loader. Schema loads failing with ‘Error while initializing engine: Engine is not valid’
  • Loader. Backport - Loads with SAP connector fail after tenant deletion
  • Loader. Data Integrity issue
  • Loader. Backport - EBS_XLA is failing with ArrayIndex Out of bound causing EBS_XLA_MV to fail to load due to missing snapshots
  • Scheduler. sendDashboard: Scheduled Dashboard not being sent when dashboard contains KPI with conditional formatting
  • Schemas. NPE while checking schemas dependency
  • Schemas. Backport - Schema shows ‘Not Completed’ after the load is finished with error java.lang.ArrayIndexOutOfBoundsException
  • Schemas. Backport - NPE while checking schemas dependency

Maintenance Pack 8 (July 2019)

The following issues were fixed in this maintenance pack:

  • Loader. Incremental load fails after upgrading to 4.3.7.
  • Loader. Fixed an issue that caused the Loader to stop working.

Maintenance Pack 7 (June 2019)

The following issues were fixed in this maintenance pack:

  • Loader. Loader Service went down unexpectedly.
  • Export. HTML export of pivot tables with multiple row fields and total set to ‘top’ fails.
  • Scheduler. Dashboards scheduler failed to send excel attachments.
  • Scheduler. Scheduler reports are failing with Required Columns not loaded.

Maintenance Pack 6 (May 28, 2019)

The following issues were fixed in this maintenance pack:

  • Dashboard. Fixed an issue where a date column did not display in the expected format after an upgrade from Incorta Analytics version 3.x to 4.x.
  • Dashboard Caching. Prior to release 4.3.6, dashboards that have an insight with $currentTime will not have any insights on that dashboard cached. This could impact the performance of dashboards. This has been fixed in 4.3.6.
  • Front-End Web. Introduced two additional timestamp formats for the Analyze User to apply within the insight for timestamp data type. The format list of values now includes yyyy-MM-dd hh:mm:ss(24hr) and yyyy-MM-dd hh:mm:ss.
  • Scheduler. Fixed an issue where scheduled jobs were automatically disabled after exporting and then importing a tenant.
  • SQL Interface. Resolved an issue with SQL Interface queries, where the base table had a security filter using external session variables and an error displayed when trying to load data.

Maintenance Pack 5 (May 7, 2019)

The following issues were fixed in this maintenance pack:

  • Schema. Fixed an issue where a schema load showed as completed in UI, but not in the log files.

Maintenance Pack 4 (May 1, 2019)

The following issues were fixed in this maintenance pack:

  • Server. Fixed an issue where you could not add a bookmark to a filter using a formula with a boolean condition.

Maintenance Pack 3 (April 23, 2019)

The following issues were fixed in this maintenance pack:

  • Dashboards. Fixed an issue where this error displayed: “Dashboard System Error. Please ask the Administrator to check the log files.”
  • Engine. Fixed an issue where joins over formulas were not working.

Maintenance Pack 2 (April 17, 2019)

The following issues were fixed in this maintenance pack:

  • CMC. Fixed an issue where the CMC Tenants tab was not accessible after creating a tenant on AWS EFS storage.
  • Materialized Views. Fixed an issue where Materialized Views did not load as expected in the NFS directory.

Maintenance Pack 1 (April 10, 2019)

The following issues were fixed in this maintenance pack:

  • Dashboards. Fixed an issue where the following message displayed while rendering dashboards: “System Error. Please ask Administrator to check the log files.” 
  • Dashboards. Fixed an issue where date values were not formatted correctly in the filter pill after creating a dashboard with a date formula, assigning default values, then refreshing. 
  • Dashboards. Fixed an issue where dashboards migrated from v3.3.1 to v4.2.6 did not load and displayed an error.
  • Formulas. Fixed an issue where formula columns removed from the schema still displayed in dashboards. 
  • Materialized View. Fixed an issue where creating a materialized view on a remote table displayed an error. 
  • Schema. Fixed an issue where opening the runtime filter, selecting a field on the left panel, switching the operator to “Is Descendant,” and then clicking on any level changed the operator back to “In.”
  • Schema. Fixed an issue where running a full data load on a schema displayed the error, “Failed to Create Loader Job.”

Release Notes for Incorta Analytics Release 4.3


  • Note that exported objects from one Incorta Analytics version are not compatible with older versions.
  • Critical prerequisites are needed for 4.3 Windows installation/upgrade. Learn more

What’s New in 4.3

Area Feature/Enhancement
Performance Enhanced extraction of large tables - That is, in-parallel query execution for extracting data from Oracle and MySQL data sources, leading to significant performance enhancement during the extraction process.
Compaction Parquet Compaction Performance - A new compaction algorithm option helps improve the compaction time for large tables (up to 2 billion rows), especially during an incremental update.
Data Sources & Data Files Data source connector SDK - The new connector SDK framework provides flexibility to add and create new data source connectors without having to wait for a new release or upgrade.
Hive connector for remote tables - Connect to ORC, Parquet and CSV files in HDFS data lakes as remote tables without loading them in memory, enabling you to use them seamlessly with other tables to build materialized views. This feature also allows connecting other BI tools (e.g. Tableau) to Incorta and use that data through Incorta.
CMC Memory Monitor - Monitor the memory usage for live analytics and loader services right in the CMC UI.
Enhanced CMC authentication - Incorta Analytics 4.3 includes an enhanced CMC authentication method and new login screen.
Display available disk space for tenants path in the CMC UI - View the available disk space for each tenant when creating one, and corresponding to each tenant under the Tenants tab in the CMC UI.
Schemas New Schema Wizard - Create schemas using with the redesigned schema wizard with a simple layout, making it more intuitive to create schemas using existing tables and custom SQL queries.
Fix Query Plan - Fix a join path for a specific Insight in a specific tenant, so that it is not affected by changes in tables or respective joins.
Preview schemas sample column data - Take a sneak peek at your column data while creating a schema in the schema wizard, or in the table details page of physical or business schemas.
Security New user and group security management UI - Create users, groups, and manage security privileges through the face-lifted security section of the web application.
Dashboards & Insights Create data alerts from the dashboard - Set a data alert for an Insight right from within the dashboard containing that Insight.
Convert charts to table Insights for viewer users - Convert a chart data visualization into a table in a dashboard, without requiring an Analyzer privilege to edit the Insight.
Display the equivalent SQL queries - View the equivalent SQL queries for table Insights, tables in schema wizards, and Materialized Views.
Export and import all of your catalog content - Export all of your dashboards and folders from the “Content” page of the web application all at once, to either migrate your work from one environment to another or simply use it as a backup.
External BI tools In-App guidance to connect to external BI tools - This release includes a trial for in-app guidance to connect to Tableau, MicroStrategy, PowerBI, or Excel.


  1. Change Zookeeper’s minimum session timeout - Incorta Analytics 4.3 reduces Zookeeper’s minimum session timeout from 90,000 to only 2,000. Learn more
  2. The CMC does not need to be up and running for Admins to reset their passwords.
  3. The HTTP ports are mandatory for loader services to start. (Loader HTTP ports are used for internal communications between nodeAgents and loader services.)
  4. When upgrading from 4.0 thru 4.2.x to 4.3, It is important to upgrade the metadata database using the following:

    • Go to the cd <IncortaInstallation>/cmc/tmt/ directory.
    • Run the command: ./ -clnm <ClusterName> -umd.

Known Issues

Deleting a schema causes Incorta to freeze. You can replicate this error using the following steps:

  1. Create two or more schemas.
  2. Create overlapping scheduled jobs.
  3. Select two schemas to delete, icluding one schema with a scheduled job.

Expected behavior: The schemas are deleted and no exceptions happen.

Actual behavior: The schemas are deleted and Incorta freezes.