Skip to main content
Version: I2024.2.x

Resolved Issues

The following issues have been resolved.

I2024.2.3​

Excessive traffic over the Engine to Engine communication channel caused by XMLA sessions could lead to engine restarts and lookup query timeouts in clustered AtScale environments​

In clustered AtScale environments (with or without Query Engine nodes), if requests containing the same XMLA sessionId occur against multiple hosts, the requests and responses for those sessions were transferred across the Engine to Engine communication channel back to the original host that registered the session. This could result in the Engine to Engine communication channel becoming overloaded, causing cube level and other session state lookups to time out. This, in turn, could lead to user query failures or restarts of the secondary Engine nodes, due to heartbeat keep alive timeouts.

This issue has been resolved. XMLA sessions are now managed so that the Engine or Query Engine node that receives a user request now processes the request and sends the response, directly avoiding the transmission of these requests over the Engine to Engine communication channel.

ATSCALE-22005

Duplicate aggregates created for some partitioned aggregates​

A condition was found where AtScale could create duplicate aggregates of partitioned aggregates. The only difference between the duplicates and the originals was the ordering of their contents. This issue has been resolved.

ATSCALE-21951

Microsoft Power BI, Excel: Reports and queries failed when SOAP.SAFE.XML.PARSING was enabled​

The AtScale Engine setting SOAP.SAFE.XML.PARSING can be enabled to prevent XXE attacks. Previously, when this setting was enabled, Power BI and Excel reports and queries would fail against AtScale. This issue has been resolved: when the setting is enabled, Power BI and Excel queries and reports should no longer fail.

note

SOAP.SAFE.XML.PARSING is disabled by default. To enable it, go to Engine > Settings and click Custom Settings. Enter the following values, then click Save.

  • Setting Name: SOAP.SAFE.XML.PARSING
  • Setting Value: true

You do not need to restart the engine after changing this setting.

ATSCALE-16773, ATSCALE-20815

I2024.2.2​

Broken Access Control Vulnerability​

Low privileged users were able to access details for private projects and cubes, such as names, descriptions, and cube/project IDs, via the API. This issue has been resolved. Authorization checks have been improved to ensure that only users with the appropriate permissions can access private project/cube details.

ATSCALE-19739

Insecure Direct Object References Vulnerability​

Low privileged users were able to update private cubes that were in a draft state via the API. This issue has been resolved. Authorization checks have been improved to ensure that only users with the appropriate permissions can edit cube details.

ATSCALE-19742

Queries failed during planning stage​

In AtScale I2024.2.1, queries occasionally failed during the planning stage. This issue has been resolved.

ATSCALE-21316

Queries were generated using unnecessary outer joins​

When fact-connected security dimensions were enabled, queries on unconnected dimensions were generated using unnecessary outer joins, resulting in slowed performance. This issue has been resolved.

ATSCALE-21133

Security dimensions were incorrectly applied to unconnected dimensions​

Security dimensions with Use Filter Key lookup rules were incorrectly applied to queries on unconnected dimensions. This resulted in multiple unnecessary lookup queries being generated for all queries. This issue has been resolved.

ATSCALE-21130

Microsoft Excel: Incorrect grand totals displayed for semi-additive measures​

In Excel, grand totals for first/last non-empty semi-additive measures displayed the same values as additive measures with an aggregation function of SUM, rather than the respective first/last non-empty value for the first/last key value defined. This issue has been resolved.

ATSCALE-21528

Excel: Queries on unrelated dimensions and measures produced syntax errors​

Queries on cubes that contained unrelated dimensions and measures produced syntax errors in Excel. This issue has been resolved.

ATSCALE-21169

Excel: Security dimensions caused failed queries​

Security dimensions occasionally resulted in failed queries in Excel. This issue has been resolved.

ATSCALE-21026

Queries canceled in Excel or Tableau remained running in Snowflake​

Queries that were canceled in either Excel or Tableau were subsequently canceled in Design Center, but continued running in Snowflake. This issue has been resolved.

ATSCALE-16832

I2024.2.1​

Hadoop recertified for I2024.2.1​

I2024.2.1 resolved query issues found with Cloudera CDP. Cloudera Hadoop and HP MapR are supported in I2024.2.1 and moving forward.

ATSCALE-21563

AtScale engine failed to start after upgrade​

After upgrading, the engine failed to start with an error from pgwire. This issue has been resolved.

ATSCALE-21572

PostgresSQL was only listening to the localhost port​

PostgresSQL was only listening to the localhost port, which caused the pgwire interface to fail on FQDN installs. This issue has been resolved.

ATSCALE-21601

Microsoft Excel: Reports containing Calculation Groups and Calculated Measures with Hidden Measures failed​

In Microsoft Excel, reports failed when they contained both a calculation group and calculated measure that contained a hidden measure. This issue has been resolved.

ATSCALE-20788

Excel: Level hierarchies with key columns >16 digits did not display properly​

Excel reports did not properly display hierarchy levels that used Long values longer than 16 digits as their key columns. When these levels were expanded, Excel created new rows, rather than displaying the full levels. This issue has been resolved.

ATSCALE-19778

Excel: ParallelPeriod Produced Incorrect MTD Values on and After Leap Years​

In Excel, MDX expressions that included the ParallelPeriod function produced incorrect MTD values on and after leap years. This issue has been resolved.

ATSCALE-20780

Microsoft Power BI Online Service: The Export Data option failed with Matrix Visual Reports​

In Microsoft Power BI Online Service, using the Export Data option from a matrix virtual report failed when both of the following conditions were true:

  • The AtScale model used in the report contained a security dimension with a lookup rule of Use Filter Key.
  • The Power BI report was created with a connection that included daxdialect=tabular or daxdialect=superdaxmd.

This scenario also caused queries to fail in AtScale. This issue has been resolved.

ATSCALE-20271

Power BI: Reports containing measures with UTCNOW() failed​

In Power BI, reports containing measures that used the UTCNOW() DAX function failed. This issue has been resolved.

ATSCALE-19848

Power BI: Incorrect outbound queries generated when Filtering by NULL and using SuperDAXMD​

When connected to Power BI using SuperDAXMD, filtering reports by NULL values incorrectly yielded no results. This was caused by incorrect outbound queries being generated in AtScale. This issue has been resolved.

ATSCALE-18260

Power BI: Calculation Group Totals Did Not Display in Some Situations​

In Microsoft Power BI, calculation group totals did not display in visualizations that had multiple measures selected and were filtered by a subset of the calculations. This issue has been resolved.

ATSCALE-20030

Power BI: Applying Multiple Degenerate Dimension Level Slicers Reset Other Slicers​

In Power BI, applying multiple slicers based on degenerate dimension levels reset other slicers in the report to All. This occurred when all slicers involved were based on degenerate dimension levels. This issue has been resolved.

ATSCALE-18032

Tableau: Date Offset Queries for MS SQL Server were not Supported with PostgresSQL Drivers​

Previously, AtScale did not support Tableau-generated Date Offset queries (e.g. Now() - INTERVAL 30 DAYS) for MS SQL Server using AtScale's Postgres interface. This issue has been resolved.

ATSCALE-20484