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


Maintenance Packs for Incorta 4.3


Incorta encourages customers to upgrade to the most recent release. Here are maintenance packs notes for this minor release.

Maintenance Pack 4.3.15

Fixed Issues

  • Fixed a corner case where dashboard scheduler to email drops few runs
  • Fixed a case where the Box token gets expired and fails the load intermittently

Maintenance Pack 4.3.14

Fixed Issues

  • Resolved a thread deadlock error that was causing performance issues in analytics.

Maintenance Pack 4.3.13

What’s New?

  • Add support for Okta security Single Sign On (SSO) integration.

Maintenance Pack 4.3.12

What’s New?

  • The snapshot writing operation is now enhanced to be atomic and lightweight.
  • Enhanced analytics query logs with more details about query processing.

Issues fixed

  • Fixed an issue that was displaying incorrect table records count during table load.
  • Resolved an issue that was preventing the creation of schema or table through the Schema Wizard due to an exception error.

Maintenance Pack 4.3.11

What’s New?

  • 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.
  • 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.
  • In 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.
  • Enhancement to clear the row set off-heap memory after an incremental load.
  • 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.
  • Disabled schema deletion while schema is loading.
  • Disabled schema editing while schema is loading from the system backend.

Issues fixed

  • 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.
  • Resolved an issue where the dashboard was still displaying old values after an incremental load had finished.
  • Resolved an issue that was preventing a job from being archived.
  • Fixed a bug that was failing to ‘materialize table’ when loading an Incorta table.
  • Resolved an issue that was giving an error when trying to simultaneously load parent and child table on two different loader nodes.
  • Resolved an issue that was displaying the wrong date in the date picker selection. / Removed browser timezone dependency for date/time formatter
  • 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.”
  • Fixed a bug that gave an error message ‘required column not loaded into memory’ on the dashboard.
  • Fixed a bug that was preventing Incorta table creation.
  • Resolved an issue that was giving an error when trying to do a schema discovery from PowerBI.
  • Resolved an issue that was failing schema full load.

Maintenance Pack 4.3.10

Issues fixed

  • 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.
  • Enhanced logging where writing snapshot for tables will also include table joins.

Maintenance Pack 4.3.9

Issues fixed

  • Loads with SAP connector fail after tenant deletion
  • Fixed an issue where converting charts to tables yielded different values
  • Fixed an issue with Table Aliases that needed to refresh automatically on base table changes
  • Fixed an issue where a schema was not able to be loaded
  • Fixed an issue where schema loads failed with ‘Error while initializing engine: Engine is not valid’
  • Resolved issue with loads that use the SAP connector
  • Resolved issue with EBS_XLA failing with ArrayIndex Out of bound causing EBS_XLA_MV to fail to load due to missing snapshots
  • Resolved issue with sendDashboard: Scheduled Dashboard not being sent when dashboard contains KPI with conditional formatting
  • Resolved issue with NPE while checking schemas dependency
  • Resolved issue with Schema when it shows ‘Not Completed’ after the load is finished with error java.lang.ArrayIndexOutOfBoundsException

Maintenance Pack 4.3.8

Issues fixed

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

Maintenance Pack 4.3.7

Issues fixed

  • 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 4.3.6

What’s New?

  • 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.

Issues fixed

  • 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.
  • 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.
  • Fixed an issue where scheduled jobs were automatically disabled after exporting and then importing a tenant.
  • 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 4.3.5

Issues fixed

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

Maintenance Pack 4.3.4

Issues fixed

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

Maintenance Pack 4.3.3

Issues fixed

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

Maintenance Pack 4.3.2

Issues fixed

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

Maintenance Pack 4.3.1

  • Fixed an issue where the following message displayed while rendering dashboards: “System Error. Please ask Administrator to check the log files.” 
  • 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. 
  • Fixed an issue where dashboards migrated from v3.3.1 to v4.2.6 did not load and displayed an error.
  • Fixed an issue where formula columns removed from the schema still displayed in dashboards. 
  • Fixed an issue where creating a materialized view on a remote table displayed an error. 
  • 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.
  • Fixed an issue where running a full data load on a schema displayed the error, “Failed to Create Loader Job.”
© Incorta, Inc. All Rights Reserved.