Skip to main content

Resolved Issues

The following issues have been resolved.

C2026.3.0​

Validation for dataset incremental indicators did not handle Integer-like columns correctly​

Although dataset incremental indicators could be Integer-like column types (Long, BigInt, Int, etc.), grace periods for incremental aggregate builds could only be defined in time units (seconds, minutes, days, etc.). When an Integer-like column was used as the incremental indicator, AtScale could not identify the data encoding scheme. This led to the system performing a full aggregate rebuild, rather than an incremental one.

This issue has been resolved. When the incremental indicator column is of an Integer-like type, you can now define the grace period as a number value. The system interprets this value to be in the same format as the incremental indicator.

Note

The previous time unit format (e.g., 100s, 1w) should still be used for Date-like incremental indicators.

For more information, see About Incremental Rebuilds and Setting Properties to Allow Incremental Rebuilds of Aggregates.

ATSCALE-44816

Duplicate outbound queries were triggered when using in-memory aggregates​

When constraint translation was enabled in the AtScale engine, using in-memory aggregates triggered duplicate outbound queries. This issue has been resolved.

ATSCALE-44673

AtScale could not be started when telemetry was disabled​

AtScale could not be started when telemetry was disabled. This issue has been resolved.

ATSCALE-44791

Count non-null and count distinct metrical attributes caused deployments to fail​

Deploying models that contained count non-null and count distinct metrical attributes failed with compiler errors. This issue has been resolved.

ATSCALE-44524

In Tableau, creating a calculated field with conditional statements and tuples that reference related dimensions resulted in an error. This issue has been resolved.

Note

This issue still occurs when using tuples that reference unrelated dimensions. For more information, see Known Issues.

ATSCALE-44501

Wrong aggregates were used for multiple dimensions based on a single dataset​

Queries on multiple dimensions based on the same dataset resulted in wrong data when aggregates were enabled. This was caused by the queries incorrectly using the same aggregate for all dimensions based on the dataset. This issue has been resolved.

ATSCALE-44334

Outbound queries for grand totals joined dimensions with fact tables using constraint translation columns, rather than key columns​

Outbound queries for grand totals joined dimensions with fact tables using constraint translation columns, rather than key columns, resulting in wrong data. This issue has been resolved.

ATSCALE-44058

AtScale generated expensive outbound queries for metrics and unrelated dimensions​

AtScale generated expensive outbound queries when metrics were selected with unrelated dimensions in reports. This issue has been resolved.

ATSCALE-43966

ADDCOLUMNS DAX function resulted in failure​

When using Microsoft Power BI in Tabular mode with Redshift, adding a Power BI client-side expression with the ADDCOLUMNS DAX function could result in errors. This issue has been resolved.

ATSCALE-25366

UDAs with multiple partitions failed to build on Databricks and Google BigQuery​

User-defined aggregates (UDAs) with multiple partitions failed to build on Databricks and Google BigQuery data warehouses. This issue has been resolved.

ATSCALE-44321

UI issues on Build tab for deployed catalogs​

Multiple UI issues on the Build tab for deployed catalogs have been resolved.

ATSCALE-42812