Skip to main content

Resolved Issues

The following issues have been resolved.

C2025.10.0​

Identity Broker did not refresh Databricks tokens when impersonation was enabled​

The Identity Broker did not properly refresh Databricks tokens when impersonation was enabled for the data warehouse. This issue has been resolved.

DEVOPS-7171

Composite models caused UDA builds to fail​

User-defined aggregate (UDA) builds failed when catalogs containing composite models were deployed. This issue has been resolved.

ATSCALE-41666

Looker: Views generated by AtScale contained incorrect metric types​

In Looker views generated by AtScale, MIN metrics were incorrectly set to type MAX. This issue has been resolved.

ATSCALE-41397

Microsoft Excel: Tuple expressions containing the [ALL] member produced wrong values​

In Excel, pivot tables displayed wrong values for tuple expressions containing the [ALL] member. This occurred when the secondary attribute from the expression was used in a pivot table row, and the attribute's hierarchy was applied as a filter. This issue has been resolved.

ATSCALE-41318

CROSSJOIN queries with mixed metric types returned incorrect results​

CROSSJOIN queries with mixed metric types returned incorrect results when query.emptyValueCrossJoin.enabled was set to true under NULL cell query conditions. This issue has been resolved.

ATSCALE-41082

The caching: engine-memory SML property disappeared after editing a deployed model's UDAs​

When a model containing UDAs was deployed, and the UDAs were subsequently edited, the caching: engine-memory property was removed from the model's SML. This issue has been resolved.

ATSCALE-40633

AtScale incorrectly displayed errors for key values​

AtScale incorrectly displayed errors stating key values were used in multiple levels/secondary attributes, when they were not. This issue has been resolved.

ATSCALE-28705

Crossing calculation groups resulted in wrong data and query planning errors​

Crossing calculation groups resulted in wrong data when the query hit an aggregate. Additionally, crossing calculation groups when aggregates were disabled resulted in a query planning error. This issue has been resolved.

ATSCALE-28475

Aggregate materializer became stuck​

The aggregate materializer became stuck. This issue has been resolved.

ATSCALE-40998

AtScale support data did not include all datasource statistics​

The AtScale support data did not include all datasource statistics. This issue has been resolved.

ATSCALE-27816