Skip to main content
Version: I2025.1.0

Resolved Issues

The following issues have been resolved.

Custom ParallelPeriod was not supported for Redshift​

The custom ParallelPeriod functionality was not supported for Redshift data warehouses in I2024.2.7. This issue has been resolved, and this functionality is now supported.

ATSCALE-24233

Microsoft Excel: Filtering on level aliases multiple times produced an error​

In Excel, filtering on a level alias more than once resulted in an error. This issue has been resolved.

ATSCALE-24527

Query cache was not functional when using PGWire​

When using the PGWire interface (port 15432), the query cache would sometimes not be utilized. This issue has been resolved.

ATSCALE-24394

Query planning failed for non-superusers​

When the query.securityConstraint.groupHandling.enabled setting was enabled, query planning failed for users without the superuser role. This issue has been resolved.

ATSCALE-23982

AtScale engine became unstable after restarting​

In I2024.2.7, the AtScale engine could become unstable after restarting, preventing BI tools from connecting and projects from publishing. This issue has been resolved.

ATSCALE-23936

The metadataExport.driver.type cube-level setting was not applied to published projects​

The cube-level setting metadataExport.driver.type was not applied to published projects, making it impossible to change the connection type for .tds files. This issue has been resolved.

ATSCALE-23931

Some MDX functions did not work with Current calculations​

The following MDX functions produced incorrect results when used with Current calculations in calculation groups: ExtractMember, Tail, NonEmpty. This issue has been resolved.

ATSCALE-24113

Aggregate creation queries canceled in AtScale continued to run in the data warehouse​

When aggregate creation queries were canceled within AtScale, only the inbound queries were successfully canceled, while the outbound queries continued to run in the data warehouse. This issue has been resolved.

ATSCALE-23330

AtScale queries sometimes used incorrect namespace convention for Databricks​

AtScale queries did not always use the correct Databricks namespace convention, resulting in long publish times and errors in both the AtScale engine and Databricks. This issue has been resolved.

ATSCALE-23934

Excel: Results for measures based on different fact tables were missing​

In Excel reports, results from one measure based on one fact table disappeared after adding a second measure based on a different fact table. This issue occurred when a dimension common to both fact tables contained a key value from one of the tables, but not the other. This issue has been resolved.

ATSCALE-23830

Semi-additive measures produced incorrect results when evaluated with quarter-to-date calculations and then used in ratios​

Calculation groups that evaluate semi-additive measures with quarter-to-date calculations, and then use the result in a ratio, produced incorrect results. This issue has been resolved.

ATSCALE-24712

Using tuples with calculated measures that combined multiple fact tables produced query planning errors​

Creating a tuple from a calculated measure that sums two measures from two different fact tables produced errors during query planning. This issue has been resolved.

ATSCALE-24445

Distinct count MDX queries did not fully trigger or use aggregates​

Aggregates weren't always triggered or used for distinct count MDX queries. This issue has been resolved.

ATSCALE-24315