Release Notes Incorta 2024.1.4
Release Highlights
This maintenance pack introduces two main features: data extraction from verified business views to different destinations in Parquet format and multiple enhancements to the SQLApp to improve resilience and address related issues.
For customers already on 2024.1.3 or prior to 2024.1.x releases, this is a low-risk maintenance pack with bug fixes and better resilience.
This release uses the Data Agent version 8.2.2. Please upgrade to this version.
The Data Agent package no longer includes the MySQL driver; you must provide your own driver.
To download and deploy the MySQL jar, do the following before starting the Data Agent service:
- From the unzipped
incorta.dataagent
directory, run one of the following scripts depending on the machine you install the Data Agent on:- For Windows, run
patch-mysql.bat <unzipped_data_agent_path>
. - For Linux, run
./patch-mysql.sh <unzipped_data_agent_path>
.
- For Windows, run
These scripts download the MySQL jar file version 5.1.48 from Maven repository and mainly deploy it to the <unzipped_data_agent_path>/lib
directory. If you already have the jar file, add the jar location when you run the script to only copy it to the required directory, for example, patch-mysql.bat <unzipped_data_agent_path> <mysql_jar_location>
.
To inspect the script's output, check <unzipped_data_agent_path>/patch-mysql.log
.
Upgrade considerations
If you are upgrading from a release before 2024.1.3, please review the Upgrade Considerations for 2024.x releases.
Starting this release, 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.
What’s New
Data extraction via Advanced SQLi and Public API
By leveraging Advanced SQLi and Public API, Incorta has streamlined data extraction from verified business views to different destinations in Parquet format. Supported destinations include Google Cloud Storage (GCS), Azure, AWS S3, and local destinations. For Cloud installations, only GCS is supported.
Data Extraction via Advanced SQLi and Public API is a labs feature.
For details about the required configurations and prerequisites, refer to Data extraction via Advanced SQLi and Public API.
For details about the related API endpoints, refer to the respective endpoint documentation.
- Create External Schema: Creates a new external schema in the Spark Metastore for data extraction.
- Extract to External Table: Creates a new external table in the Spark Metastore, extracts data from the specified business view, and saves the Parquet files to the specified path. You can also replace the external table if exists.
- Append to External Table: Extracts data from the specified business view and adds the Parquet files to the path associated with an existing external table.
- Delete External Table: Removes the external table definition from the Spark Metastore.
- Delete External Schema: Removes the external schema definition from the Spark Metastore.
- You must delete all external tables in a schema before deleting the external schema itself.
- Deleting external tables or schemas only removes their definition from the Spark Maetastore. You must delete the respective Parquet files manually from the related paths.
SQLApp Enhancements
Previously, both the Analytics and the SQLi services could start SQLApp, which resulted in resilience issues and scattered logs. The new enhancements aim to improve resilience and address recent issues related to SQLApp.
Ownership and Startup
- Only the SQLi service can start SQLApp. As a result, the SQLi service must be started and the Spark port must be enabled when creating or running Incorta-over_Incorta tables or SQL views based on non-optimized tables.
- Starting a SQLi service will start its associated SQLApp and terminate any existing SQLApp.
- Shutting down a SQLi service will shut down the associated SQLApp.
Logging Improvements
- Logs are now appropriately managed and not cluttered within the Analytics services.
- Enhanced SQLApp logging for easier troubleshooting.
Connection Throttling
A new CMC option (Server configurations > SQL Interface > Max number of concurrent connections from SQLi to SQLApp) is now available to control the maximum number of connections from SQLi and SQLApp, the default is 100.
When the limit is reached, the SQLi service waits for a configurable interval (5 minutes by default) before trying to acquire a connection to SQLApp. If it fails to acquire a connection after this interval, it throws a timeout exception.
Enhancements
Enhancement | Area |
---|---|
Incorta now bundles Apache Tomcat 9.0.89 and Spark 3.3.4 to catch up with the security enhancements and fixes in these versions. | Security |
The dropdown Slicer component now displays the value of the selected date presentation variable instead of the variable name. However, the selected variable’s name and value appear when opening the dropdown list. | Slicer Component |
In chart visualizations, long measure names are now truncated, and missing characters are replaced with ellipses (…) instead of trimming the name. | Visualizations |
Fixes
Fixed Issue | Area |
---|---|
For On-Premises installations, attempting to browse the Advanced SQL (Beta) section under the Connect to Other Visualization Tools > Tableau page resulted in an error. | Advanced SQLi |
An issue with the unique index sequential calculation intermittently caused the failure of loading tables and join calculations during Post-load. | Loader Service |
An issue with the Stacked Column visualization resulted in assigning the same color to different values when drilling down from other dashboards. | Visualizations |