Codebase Migration

Add the migration adapter dependency to your project:

<dependency>
  <groupId>org.gridgain.ignite</groupId>
  <artifactId>migration-tools-adapter</artifactId>
  <version>1.0</version>
</dependency>

Create the GridGain 9 client instance:

// In a separate scope or using the full qualified name.
// Create a client instance configured to connect your GridGain 9 cluster.
var ignite3Client = org.apache.ignite3.client.IgniteClient.builder()
    .addresses("127.0.0.1:10800")
    .build();

//Create your desired Ignite 2 interface.

// Thick client
try (IgniteAdapter adapter = IgniteAdapter.builder(ignite3Client)
    .allowExtraFields(true)
    .build()) {
    //...
}

// Thin client
try (IgniteClient adapter = IgniteClientAdapter.builder(ignite3Client)
    .allowExtraFields(true)
    .build()) {
    //...
}

Setting allowExtraFields to true (default) allows extra fields in the Java client adapter. If you migrate a cache in the PACK_EXTRA mode, you can access additional fields in that cache - those that were not converted directly to columns.

Setting allowNonDefaultConstructors to true (false by default) enables mapping Java classes that do not define a default constructor. This is not supported natively in GridGain 9. Therefore, we encourage you to implement default constructors in your data classes instead of allowing non-default constructors. The latter relies on unsafe mechanisms and introduces a modest performance penalty.

tableTypeRegistry provides mappings between tables and the corresponding Java classes. In GridGain 8, this information is persisted to a system view, which can be overridden locally by individual records. Currently, the default implementation is stored in a persistent table.