Migration Guide
This article describes actions required for migration between major versions of AggreGate.
Migration from Version 5.5X.XX to 5.6X.XX
This guide will help you to prepare your AggreGate Server for upgrading from 5.5.x to 5.6.x version.
Please make a backup of AggreGate Server folder and all databases used in your project.
NoSQL Event Storage (Cassandra) Preparation
This guide helps you to update your embedded NoSQL storage before AggreGate Server update. AggreGate Server of 5.4.x, 5.5.x and 5.60.01 versions uses Cassandra 2.0.12. AggreGate Server uses Cassandra engine of 3.11 version so we should update it to the current version before first launch of 5.6.x version.
The order of necessary steps is described below:
hints_directory, data_file_directories, commitlog_directory, saved_caches_directory parameters in cassandra.yaml configuration file. It should be targeted to current Cassandra DB folder inside AggreGate Server (nosql_data folder)nodetool upgradesstables from separate Cassandra server's bin folder.You should repeat steps 2-6 for 2.2, 3.0 and 3.11 versions of Cassandra server.
Expressions Update After Migration to 5.6.x Version
We updated protocol to reduce amount of metadata. So we removed extra encoding symbols from it.
You can find extra % symbols in some expressions. In older versions of our platform we stored them in DB. So you should remove extra % symbols from your expressions and save your changes. After this operation the correct data will be saved to configuration DB and will work fine in 5.6.x version.
Scripts Update
Since Java API was modified in the new version you'll also need to change your scripts in Java. In particular you'll need to change all your instructions with DataTable class (e.g. DataTable dataTable = new DataTable()) to instructions using SimpleDataTable (SimpleDataTable simpleDataTable = new SimpleDataTable()).
Was this page helpful?