Skip to main content

Known Issues

AtScale contains the following known issues.

C2026.2.0​

Partition-based incremental aggregate builds require incremental indicator columns to be a date-like type​

There is a known issue with partition-based incremental aggregate builds that arises when the incremental indicator column is a number type, such as Long, Decimal(38,0), or BigInteger. When using such a type, the incremental build routine does not correctly convert the grace period time offset and rebuilds more records than specified by the grace period parameter. This issue does not affect models that use an incremental indicator column of a date-like type, such as Date, Timestamp, or DateTime.

ATSCALE-44816, ATSCALE-44814

Duplicate outbound queries triggered when using in-memory aggregates​

When constraint translation is enabled in the AtScale engine, using in-memory aggregates triggers duplicate outbound queries.

If you need to use in-memory aggregates, AtScale recommends setting the query.partitionConstraints.enabled global setting to false to prevent these duplicate queries. Be sure to restart the engine after updating the setting. Note that this setting is enabled by default.

ATSCALE-44673

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

User-defined aggregates (UDAs) with multiple partitions fail to build on Databricks and Google BigQuery data warehouses. If you use either data warehouse platform, and you currently have any UDAs with multiple partitions in deployed catalogs, AtScale recommends manually disabling them, as they may break batch aggregate builds.

ATSCALE-44321

PostgreSQL deployment update​

What you need to know​

AtScale utilizes PostgreSQL for its metadata store. When PostgreSQL is configured for high availability (with more than one replica), Bitnami’s PostgreSQL has a serious bug in its management of primary nodes, resulting in poor management and recovery services that can lead to duplicate primaries, platform instability and data loss. The result is that deploying AtScale with embedded PostgreSQL and a replica larger than one will likely create platform instability as Kubernetes auto-manages the cluster.

For environments that don’t require high availability​

AtScale will continue to ship Bitnami PostgreSQL with the default setting of replica=1. This configuration is effective and highly stable. It’s a solid configuration for POCs and non-production environments. Some customers may choose to run this configuration in production and utilize PostgreSQL’s backup options.

For environments that require high availability​

While AtScale has offered the embedded PostgreSQL for convenience, it is common for technologies that require a metastore, such as PostgreSQL, to leverage an externally managed database. AtScale recommends considering your SLAs when configuring production. If you require high availability, it is recommended that you configure AtScale with an external PostgreSQL (i.e., Amazon RDS) instance that can guarantee this SLA and ensure stability.

DEVOPS-7216

Enabling honeybee on PostgreSQL data warehouses causes engine instability​

Enabling honeybee on a PostgreSQL data warehouse after it has been connected to AtScale causes the engine to become unstable. To avoid this issue, AtScale recommends enabling honeybee on your PostgreSQL data warehouse before adding it in Design Center.

ATSCALE-28082

ADDCOLUMNS DAX function results in failure​

When using Microsoft Power BI in Tabular mode with Redshift, adding a Power BI client-side expression with the ADDCOLUMNS DAX function can result in errors.

ATSCALE-25366

Is Aggregatable cannot be disabled on non-root levels in hierarchies with more than two levels​

In hierarchies with more than two levels, disabling the Is Aggregatable property on levels other than the root level is not supported. In future releases, models with such a configuration will not deploy to the engine.

ATSCALE-25328

Iris JDBC does not support CTEs​

The Iris JDBC driver does not support Common Table Expressions (CTEs), so the new feature that enables the query planner to use CTEs is not supported for Iris. If you are using AtScale on Iris, you need to set the following global setting:

query.planning.allowCtes: false

By default, this setting is set to true.

Identity Broker logout does not completely log out of Design Center​

Users who log in to the Identity Broker from Design Center, then log out of the Identity Broker, are not automatically logged out of Design Center. This is because the Identity Broker logout event interrupts the Design Center function.

ATSCALE-22180

Tableau: Double dashes in catalog names creates empty .tds files​

Double dashes (--) in the unique names of catalogs causes corruption of Tableau .tds file generation. This is because double dashes are reserved in many databases, and signal a comment in SQL. AtScale recommends avoiding this character pattern when creating and deploying catalogs.

ATSCALE-16605, ATSCALE-22167

Perspectives cannot contain multiple objects with the same display names​

Perspectives cannot contain references to multiple objects with the same display names/labels, as this results in errors at deploy time.

ATSCALE-22326