Skip to main content

Migration Considerations

Offering a new micro-service architecture, optional code-first development (SML), and source control integration, containerized AtScale (Cxxxx.x.x) is a major step forward for customers. If you currently use an installer-based version of AtScale (xxxx.x.x or Ixxxx.x.x) and would like to upgrade to containerized, be aware that you must perform a full re-installation.

Also be aware that when upgrading, you need to migrate your existing projects and models to the AtScale Semantic Modeling Language (SML) and integrate with source control. For more information, see the following sections.

Migrating Projects To SML​

When you upgrade to containerized AtScale from an installer version, you must migrate your existing projects and data models to SML. For migration assistance, contact AtScale Support.

SML was designed to fully migrate AtScale data models. In some cases, containerized AtScale will support a concept in SML, but the UI is under development. Examples include:

  • User defined aggregates (ATSCALE-16476)
  • Perspectives (ATSCALE-16473)
  • Drill-throughs (ATSCALE-16472)

For more information on SML, see the AtScale SML Object Documentation on GitHub.

Git Integration​

Integration to source control offers customers:

  • Multi-developer experience
  • Robust CI/CD capabilities

Integrated source control also offers the opportunity to rethink how to manage modern development practices. An AtScale customer can continue to develop in much the same ways as they do in installer AtScale, but containerized AtScale requires Git integration (e.g. GitHub, GitLab).

For more information on Git integration, see Managing Git.

Organizations deprecated​

Containerized AtScale introduces an enterprise grade Identity Broker into the stack to enhance access controls throughout the product. In lieu of artificial divisions (organizations), AtScale's roadmap is to manage access via RBAC rules. Design-time RBAC is managed at the source control level (e.g. Git) and runtime permissioning at the data model level.

Stat jobs rerun after migration​

Due to an architectural change in how AtScale stores data statistics, table stats must rerun after a migration from installer-based to containerized AtScale.

ATSCALE-18180