Migration notes 2.1

This page explains the changes required to migrate to the stated version of Atoti Common Library.

Migrate to 2.1.3-AS6.1

Headline announcement

• Bug fixes: This release contains several bug fixes.

Bug fixes

• Upgrading Atoti Common Library to Atoti Server 6.1.4 resolved multiple issues.
• Date slicer hierarchy and post-processor now work without a static date.

Migrate to 2.1.2-AS6.1

Headline announcement

• Migrator: You can register an extra store that is not part of the star schema.
• Hierarchies: You now have an option to expand all the data along an analysis hierarchy.
• Aggregators: Introduced an aggregator that keeps only a single value.
• Bug fixes: This release contains several bug fixes.

Migrator

When using the onlyIncludeStoresInStarSchema you can now add extra tables in the migration process by calling tablesToIncludeOutsideStarSchema(...) to connect extra remote tables.

The function cloningTablesLocally(...) hasn’t changed and still connects a remote table and a cloned in-memory store.

Hierarchies

You can expand the facts along an analysis hierarchy with a simple expansion procedure. See Analysis Hierarchy Expansion Procedure.

Aggregators

The aggregator KEEP_ONLY_ONE returns a value when the collection to aggregate contains only one single member. See Keep Only One Aggregation Function.

Bug fixes

• The DATASTORE_TICK stream deadlock upon commit is fixed.
• The cluster REST address now looks like "protocol://host:port/contextPath", the cube unique name is still "cubeName/host:port".
• ConstantHierarchy.Description::withLevelPaths is fixed to work properly with slicing hierarchies.
• DateSlicerHierarchy and HierarchyWithExtraStoreFields no longer track a store’s modification line by line, but instead register a commit callback and perform a “SELECT DISTINCT” query.

Migrate to 2.1.1-AS6.1

Headline announcement

• DirectQuery validation timeout: A new property allows you to specify the timeout used by DirectQuery for table validation queries.

DirectQuery validation timeout

The following property has been added: directquery.schema.validation.table-validation-query-timeout.

This property accepts a duration that is used as the timeout for table validation queries run at application startup. The default value is 1 minute.

Migrate to 2.1.0-AS6.1

Headline announcement

• Atoti Server upgrade : Atoti Common Library has been upgraded to Atoti Server 6.1.0. For the required changes, see Atoti Server upgrade.

Atoti Server upgrade

For details on migrating your code to Atoti Server , see the Atoti Server migration notes.

Java 21

Update your Java version to Java 21 or later in order to run Atoti Common Library.