Known Issues in 2022 Releases
The following are the known issues in the cloud releases starting 2022.1.0 along with the workaround and fix version if any.
| Known issue | Status | Affected Versions | Workaround | Fix Version |
|---|---|---|---|---|
| When enabling Spark-based extraction on a data source while running Spark 3.3, the extraction of the respective table fails. | Open | Spark 3.3 | Turn off the Enable Spark Based Extraction in the Table Data Source or Edit Dataset dialog. | |
| Running total is not displayed correctly when the measure has null values. | Resolved | 2022.12.0 -2023.7.x | 2024.1.0 | |
| A formula column that only references a physical column with null values shows wrong results as the Loader Service does not respect the null values when materializing the formula column. | Open | 2022.12.0 and later | ||
The count and distinct functions return null values instead of zeros when using them in a flat table or a session variable. | Open | 2022.12.0 and later | ||
| Applying an average aggregation on a decimal column with null values only throws an error and causes the insight to fail to render. | Resolved | 2022.12.0 - 2023.7.x | 2024.1.0 | |
| PK index calculations take a long time during load jobs when there are a large number of segments or increments to check. | Resolved | 2022.11.0 - 2022.12.x | Do one or more of the following: ● Contact Incorta Support to merge these segments and reduce their number. ● Create a materialized view or Incorta-over-Incorta table that consumes these segments and creates a less number of segments. ● Contact Incorta Support to edit the Loader Service engine.properties file and set the new option store.offsets_exists_parallel to true. This option is available starting 2023.1.0 and requires a lot of resources. Thus, it is suitable for very large clusters. | 2023.1.0 |
| When multi-schema loading is enabled, adding a load plan from Schema Manager doesn’t display the total number of schemas correctly. | Resolved | 2022.11.0 | 2022.12.0 | |
| Numeric Range Slicer does not function properly with variables | Resolved | 2022.9.0 - 2022.10.0 | 2022.11.0 | |
| When the Pause Scheduled Jobs option is enabled in the Cluster Management Console (CMC), the emails of manually activated scheduled jobs are not sent. | Open | 2022.9.0 and later | ||
| Scheduled jobs of overwritten dashboards and physical schemas are not deleted. | Open | 2022.9.0 and later | ||
| The “You have successfully deleted 1 schema(s)” message is erroneously displayed when trying to delete a physical schema while loading it. | Resolved | 2022.9.0 - 2022.10.0 | 2022.11.0 | |
| Access rights to a parent folder are not propagated to child folders and dashboards if the same access rights were revoked before. | Open | 2022.9.0 and later | ||
| Aggregated tables with hierarchical data do not support conditional formatting based on other measures when adding multiple attributes. | Open | 2022.9.0 and later | ||
Exporting a tenant with a global variable that uses the newly supported syntax (query or queryDistinct expressions) from a cluster that runs a release prior to 2022.5.1 and then importing it to a cluster that runs the same or a later release will cause the Edit Global Variable dialog to show an empty Value. | Open | 2022.4.0 - 2022.5.0 | You can manually edit the value to enter the query expression again or upgrade both of the source and target clusters to the 2020.5.1 release before exporting the tenant that you want. Note: This issue does not apply to exporting a tenant from a cluster that runs 2022.5.1 or a later release and then importing it to the same or another cluster that runs 2022.5.1 or later. | |
| No validation on functions is triggered in the Formula Builder when creating global variables. | Open | 2022.4.0 and later | ||
| Global Variables that return a list of values are not functioning properly when referenced in materialized views (MVs) or individual filters. | Open | 2022.4.0 and later | ||
Global Variables will not appear on the list of variables when referenced in a column individual filter, that is when you type $ in the Search Values box. | Open | 2022.4.0 and later | You can add the global variable manually, if applicable. In Query, Contains, and Starts With are examples of functions that accept a global variable as a filter value to be added manually. | |
Using the DISTINCT operator on a measure in a Pivot table that is built over an Incorta SQL View throws errors. | Open | 2022.4.0 and later | ||
| In an imported physical schema or tenant, the Disable Full Load option will be automatically enabled after changing the data source of an object to an Incorta SQL Table or vice versa, which will lead to skipping these updated objects in the next schema full load jobs. | Open | 2022.3.0 and later | You need to either disable the feature manually for objects that support disabling full loads (physical schema tables and MVs with incremental load enabled) or recreate the objects. Note: This issue does not apply to newly created Incorta SQL Tables. | |
| Incrementally loading a table without a key for the first time results in an error. | Open | 2022.3.0 and later | Attempt to load the table incrementally again | |
| Insights might not render when you run the same query multiple times for the same dashboard. | Open | 2022.3.0 and later | ||
| Email addresses added as CC or BCC in a scheduled data notification are not saved. | Open | 2021.4.3 and later | ||
| An incremental load job on a schema skips PostgreSQL MVs that reference business views and use a parameterized query statement. In addition, the MV load type shows full load (F) instead of incremental (I). | Resolved | 2022.11.0 | 2022.11.1 | |
| Dashboard names with special characters will not be displayed correctly when sending the dashboard via email. | Resolved | 2022.9.0 | 2022.10.0 | |
| When you close the browser while you have unsaved (unpublished) changes on physical schemas, these physical schemas are locked and other users will not be able to edit them. | Resolved | 2022.3.0 - 2022.6.0 | To unlock these physical schemas, you can either publish your changes or discard your draft version. In addition, these physical schemas will be automatically unlocked after 5 minutes. | 2022.7.0 |
| In the Schema Designer, a warning message is not displayed when enabling the encryption option for a Key column. | Resolved | 2022.3.0 - 2022.5.1 | 2022.6.0 | |
| Global variables with a date or timestamp data type are not evaluated properly when referenced in the Analyzer. | Resolved | 2022.4.0 - 2022.5.1 | 2022.6.0 | |
| Formula columns that reference global variables are evaluated as a string in the following cases: ● Importing a tenant ● Restoring a tenant ● Starting up a server ● Starting up a cluster | Resolved | 2022.4.0 - 2022.5.0 | 2022.5.1 | |
Incremental load jobs of tables with SQL-based data sources, such as Microsoft SQL Server and Oracle, will fail if the Incremental Script has multiple conditions with the ? option to retrieve new and updated data. | Resolved | 2022.4.0 - 2022.5.0 | 2022.5.1 | |
| Changing the script language used for a loaded MV from Spark SQL to Incorta PostgreSQL throws errors. | Resolved | 2022.4.0 | 2022.5.0 | |
| Updating the bookmark for dashboard with an applied filter after editing the filter results in an error. | Resolved | 2022.3.0 | 2022.4.0 | |
The In operator is missing in the security runtime filters operators. | Resolved | 2022.3.0 | 2022.4.0 | |
| The Geo Column type is missing in the column type list. | Resolved | 2022.3.0 | 2022.4.0 | |
| In the Schema Designer, for a given unloaded object, the Preview Data button is enabled instead of being disabled. | Resolved | 2022.3.0 | 2022.4.0 | |
| In the Schema Designer when a table requires stage loading, the warning message "Full load required for a new model to take effect" appears instead of "Staging load required for a new model to take effect". | Resolved | 2022.3.0 | 2022.4.0 | |
| Notebook auto-complete for Spark Python is not working as expected. | Resolved | 2022.2.0 | 2022.3.0 | |
| Schema load logs for MVs are missing the following when entering the transforming phase: HA, Task, Schema Name, Table Name, Job ID, Job Type (Transforming), ETL, and Load Type (INCR). | Resolved | 2022.2.0 | 2022.3.0 | |
| Box authorization error for a new connection | Resolved | 2022.2.0 | 2022.3.0 |