1. Home
  2. Other Releases
  3. On-premises 5.2
  4. Guides
  5. Tours
  6. Concepts
  7. Tools
  8. References
  9. Integrations
  10. Data applications
  11. Releases
    1. Release Model
    2. Release Notes 5.2
    3. Release Notes 5.2.1
    4. Release Notes 5.2.2
    5. Release Notes 5.2.3
    6. Release Notes 5.2.4
    7. Release Notes 5.2.5
    8. Release Notes 5.2.6
    9. Release Notes 5.2.7
    10. Release Notes 5.2.8
    11. Release Notes 5.2.9
    12. Release Notes 5.2.10
    13. Release Notes 5.2.11
    14. Maintenance Packs
    15. Known Issues

Release Notes 5.2.6

The 5.2.6 release introduces the new query timeout feature. In addition, there are several enhancements and fixes that aim to stabilize Incorta and enhance its performance.

Upgrade considerations

Incorta has implemented an enhancement to address SQLi queries involving user-defined or unresolved joins within Incorta Engine. In scenarios where the Engine cannot identify a suitable query plan, it falls back to Spark and executes the original user-defined query. However, it's important to note that as a result of these improvements, the outcomes of existing queries may vary compared to previous releases. To maintain consistency with previous results, it is recommended to review these queries accordingly.

What’s new?

Query timeout

New configurations are now available in the Cluster Management Console (CMC), Tenant Configurations > Tuning > Query timeout and Query timeout (in minutes), to set a time limit after which running queries will be terminated automatically, releasing the read lock acquired on the related entities and freeing the resources reserved by these queries. These configurations affect querying data in the following scenarios:

  • Creating an insight
  • Rendering a dashboard
  • Sending a dashboard via email or to a data destination
  • Downloading a dashboard as CSV or Excel
  • Previewing a chart as a listing or aggregated table
  • Creating or updating an Incorta Analyzer table or view
  • Exploring the data of a table or view
  • Creating a data notification condition

The system tracks queries that are automatically terminated, and it records them in the system logs. In addition, a message will be displayed if applicable.

Zookeeper logging enhancements

Incorta enhanced the zookeeper logging for better performance. Starting this release, you can find the zookeeper logs in the IncortaNode/zookeeper/logs directory.

Incorta creates three files as follows:

File nameDescription
zookeeper.logIt has the information log level for zookeeper.
zookeeper_trace.logIt has the trace log level.
zookeeper_audit.logIt has the audit log data if it's enabled.
You can enable it by setting the configuration in the IncortaNode/zookeeper/con/zoo.cfg file.

Incorta rolls the zookeeper log files as follows:

  • Incorta creates a separate log file for each day.

  • If the log file size exceeds 1GB, Incorta creates a new log file for the same day and archives the previous one in the following format: <file-name>.<date>.log.gz.

    Note

    If your log files need to be more than 1GB, please contact Incorta Support. If there is more than one archived log file for the same day, override the previous one.

  • At the end of each day, Incorta archives the log file in a .gz format. The naming convention for the archived logs is <file-name>.<date>.log.gz.

  • Incorta keeps an archived log file for 10 days only. Afterward, it deletes the oldest log file automatically.

Enhancements and Fixes

In addition to the enhancement mentioned above, this release introduces other enhancements and fixes that help make Incorta more stable, engaging, and reliable.

Issue resolvedArea
Tables based on Google Sheets intermittently failed with an error: No SpreadSheet with name… found.Connectors
Error during extraction phase while refreshing tokens for Google Drive and Google Sheets.Connectors
Data lake connections were kept open leading to failures.Connectors
Wrong column mapping in Oracle B2C connector.Connectors
java.lang.NoClassDefFoundError error while doing an incremental load.Connectors
Intermittent failure during schema load from Google Drive.Connectors
Inability to export dashboards with multiple tabs having formula columns as PDF.Dashboards
INC_04050702: The underlying data for this insight is being updated, Cannot get read lock on Resources error when rendering insights while using external session variables.Dashboards
INC_04050656: Error while applying security filter error when trying to apply an invalid filter.Dashboards
Filters not updated in shared dashboards with view access when bookmarked.Dashboards
Error when downloading a whole tab as PDF.Dashboards
Using a session variable via a presentation variable in a dashboard title didn’t resolve properly.Dashboards
Inspector tool creating an empty minifiedLineageReport CSV file.Inspector Tool
Both the Loader and Analytics services took much time to start up after performing an upgrade.Loader and Analytics Services
Invalid license expiry message.Miscellaneous
Schema synchronization would be blocked from completion after a dashboard query.Physical Schemas
Creating multiple formula columns in one session results in all of these copied from the first created one.Physical Schemas
java.lang.ArrayIndexOutOfBoundsException when trying to load an Incorta Analyzer table in a full schema load.Physical Schemas
Queries with joins or conditions that Incorta Engine couldn’t identify returned inaccurate results whether Incorta Engine managed to handle them or it fell back to Spark to run them.SQLi
Using ORDER BY in a SQLi query resulted in falling back to Spark.SQLi
Heatmap doesn’t show negative correlation in the right bar.Visualizations
The Advanced Maps visualization didn’t distribute the threshold values uniformly, causing most data values not to be significantly represented.Visualizations
The Advanced Maps visualization didn't honor the color palette.Visualizations