Skip to main content

Resolved Issues

The following issues have been resolved.

C2025.3.1​

Engine inconsistencies​

Multiple issues related to inconsistencies in multi-engine AtScale deployments have been resolved.

ATSCALE-25717, ATSCALE-25750, ATSCALE-25649, ATSCALE-26356, ATSCALE-25010, ATSCALE-24423

Tableau Server integration​

Multiple issues related to Tableau Server integration have been resolved.

ATSCALE-25271, ATSCALE-24789

Adding metrics or dimensions in Tableau Server resulted in an error​

When the tableau.rawSqlAggs.enabled global/model setting was enabled, adding metrics or dimensions in Tableau Server resulted in an error. This was caused by client-side overrides to metric aggregation.

This issue has been resolved. AtScale can now be configured to prevent client-side aggregation in Tableau Server and Tableau Desktop via the new query.language.sql.preventClientSideAggregation global setting. When enabled, all metrics in .tds files are sent as either averages or distinct counts, and client-side aggregation cannot be performed. This setting is disabled by default. For more information, see Query Settings.

ATSCALE-26286

Expired data warehouse tokens blocked AtScale engine startup​

When a data warehouse had an expired or incorrect token, the AtScale engine got stuck while invalidating aggregates and timed out. This issue has been resolved.

ATSCALE-25826

Redis connections timed out​

The AtScale engine could not connect to Redis after multiple attempts. This issue has been resolved.

ATSCALE-25202

Multiple MDX functions caused errors during query planning​

Queries containing the ExtractMember, Tail, NonEmpty, and Descendants MDX functions caused errors during query planning. This occurred when the expressions contained static references to the All member. This issue has been resolved.

ATSCALE-25836

PostgreSQL interface returned errors for numeric result sets​

When using AtScale with the PostgreSQL interface, the interface returned errors for numeric result sets. This was because, in some circumstances, it expected the results to be formatted in binary, not numeric values.

This issue has been resolved: The internal AtScale PostgreSQL server now returns result sets in the format expected by the PostgreSQL interface.

ATSCALE-25856

Warning during TLS Certificate hashing when installing or upgrading​

The warning during TLS Certificate hashing when installing or upgrading has been fixed.

Engine init container failed due to missing OpenSSL on azul/zulu-openjdk image​

The engine init container failed due to missing OpenSSL on the azul/zulu-openjdk image. This issue has been resolved: azul/zulu-openjdk has been replaced with atscaleinc/engine-certs.

DEVOPS-6558

Self-signed certificates did not generate properly​

Self-signed certificates did not generate properly. This issue has been resolved.

DEVOPS-6576

Generation of ATSCALE_CRYPTO_KEY environment variable​

Generation of the ATSCALE_CRYPTO_KEY environment variable has been fixed.

DEVOPS-6572

AtScale containers will automatically restart when TLS certificates are replaced​

AtScale containers will now automatically restart when TLS certificates are replaced.

DEVOPS-6593

Engine logging level was wrong​

The default logging level on the AtScale engine pod has been updated to be less verbose.

DEVOPS-6641

C2025.3.0​

XIRR was not supported on Redshift and Databricks data warehouses​

Previously, the XIRR MDX function was not supported on Redshift and Databricks data warehouses. This issue has been resolved, and the function can now be used on both. Note that when using XIRR on Redshift, there are some requirements and limitations. For more information, see XIRR.

ATSCALE-24882

Replicated entitlement service was interrupting license check-in​

If the entitlement service was set to replicate during installation, the license was checked into the AtScale License Server, but replicated entitlement services did not have the license cached. This caused the system to behave as though a license had not been uploaded. This issue has been resolved.

DEVOPS-6116

Design Center displayed a Failed status for models that had deployed successfully with errors​

When a model was deployed successfully but contained errors, Design Center showed the deployment status as Failed. This issue has been resolved: Design Center now shows the deployment status as successful and logs a descriptive message about the errors in the console.

ATSCALE-24971

Tableau Desktop returned empty list of measures and dimensions when using the PostgreSQL JDBC 42.7.5 driver​

When using the PostgreSQL JDBC 42.7.5 driver to connect to AtScale, Tableau Desktop displayed an empty list of measures and dimensions in reports, and red exclamation points next to each field name in the Data Source tab. This issue has been resolved.

ATSCALE-24887

.tds files could not be downloaded for deployed models whose query names contained slashes (/)​

.tds files could not be downloaded for deployed models whose Query Name values contained slash characters (/). This issue has been resolved: The Query Name field of the Deploy panel no longer accepts slashes.

ATSCALE-24833

Tableau: Wrong values displayed for calculation groups when using the Postgres driver​

When using Tableau with the Postgres driver, reports contained incorrect values for some calculation groups. This was caused by uncontrolled client-side aggregation in Tableau.

This issue has been resolved. AtScale can now be configured to wrap metrics and calculations in the Tableau type-specific rawsqlagg_* function call, which prevents Tableau from aggregating the data on the client-side when collapsing the hierarchy.

This functionality is disabled by default, but can be enabled at both the global and model levels using the new tableau.rawSqlAggs.enabled setting. For more information, see Tableau Settings and Other Model Settings.

Important

If you use AtScale's calculation groups feature with Tableau, it is highly recommended that you enable this setting to avoid client-side data aggregation that will produce incorrect results.

ATSCALE-25237