0

Incorta Analytics Version 3.3 Release Notes

The following table includes a list of the features and main fixes in version 3.3. For version 3.1.10 release notes, please see Incorta Analytics Version 3.1.10 Release Notes.

WARNING: If you are upgrading from a pre-2.9.2 release, system administrators MUST run the migration tool "migrateScheduledJobs.sh" in order for schemas with existing auto-refresh jobs to continue working. This tool is shipped with the Incorta Analytics package, in the "<INSTALLATION_PATH>/bin" directory. If the migration tool is not run, schemas will stop refreshing automatically. Learn more

Area Feature/Enhancement
Data Hub Incorta analytics 3.3 introduces Data Hub. Data Hub is a tool that enables Incorta to act as a PostgreSQL database, enabling users to utilize Incorta's powerful engine performance and features, even through other BI tools (e.g. Tableau, MicroStrategy, Power BI).
For example, Users can choose to load their data into the Incorta engine (memory) so that they can take advantage of its robust performance. Or, users can opt to load their data into Incorta's staging area (if the data is too large for the Incorta assigned memory), and access this data from other BI tools through the SQLi port set in the admin UI.
Installer Incorta Analytics installer now bundles Spark as part of the installation, offering the option to either go with the default values (or change them), or configure a separate Spark installation.
Security Incorta Analytics release 3.3 includes enhanced password security measures, specifically with data sources, email, and non-Incorta applications integrations (e.g. Google Drive, Box).
Compaction This release enables users to create dashboards that monitor the Java compaction jobs, by creating a schema containing the compaction tables:
  • "COMP_DETAILS" - to monitor the active jobs, and
  • "COMP_DETAILS_HISTORY" - for a log of the past compaction jobs.
Users can then schedule that schema to load automatically, for the dashboard to reflect this data.
Filters This release includes enhancements to filters, enabling users to select (or paste) more than one value separated by commas or line breaks. This feature only works with filter operators resulting in string values, i.e. In, Not in, Contains, Does Not Contains, Starts With, and Does Not Start With.
Incorta Analytics now offers the option of mandating filter values to be case-sensitive. when using operators resulting in string values, i.e. In, Not in, Contains, Does Not Contains, Starts With, and Does Not Start With.
Known Issues    When creating a table (e.g. CSV) with an epoch column, and the date and timestamp format are epoch, the column will initially be discovered as "Integer" or "long". To solve this, the user would have to manually set the data type to "Date" in the table details page.
In this release, importing schema tables with epoch date/timestamp format from release 3.3 to an older one will cause the tables to get rejected. To resolve this issue, change the timestamp to some other date format after importing the tables, in the data source definition window.
Reply Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
Like Follow
  • 5 mths agoLast active
  • 404Views
  • 1 Following