Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Apache Ignite 2.0 is based on the new page memory architecture. Data is always stored offheap, with ability to optionally cache small portion in Java heap. Please refer to documentation to learn more about new concepts and configuration parameters [1]. 

Asynchronous programming

IgniteAsyncSupport interface is now deprecated and will be removed in future Apache Ignite releases. Use methods with Async suffix instead. See documentation [4] for more information.

Old style:

Code Block
IgniteCache<K, V> asyncCache = cache.withAsync();
 
asyncCache.getAsync(key);
 
IgniteFuture<V> future = asyncCache.future();

New style:

Code Block
IgniteFuture<V> future = сache.getAsync(key);

Thread pools

Ignite process different types of requests in special thread pools to provide clear separation of concerns and avoid starvation. Several new thread pools were added in Apache Ignite 2.0:

...

SPI has been removed due to new Ignite page memory architecture [1]. The swapping tier can only be used if a swapping file is set via MemoryPolicyConfiguration.swapFilePath property.

General API

Asynchronous programming

IgniteAsyncSupport interface is now deprecated and will be removed in future Apache Ignite releases. Use methods with Async suffix instead. See documentation [4] for more information.

Old style:

Code Block
IgniteCache<K, V> asyncCache = cache.withAsync();
 
asyncCache.getAsync(key);
 
IgniteFuture<V> future = asyncCache.future();

New style:

Code Block
IgniteFuture<V> future = сache.getAsync(key);

IgniteCluster 

  • mapKeysToNodes - removed, use Affinity.mapKeysToNodes
  • mapKeyToNode - removed, use Affinity.mapKeyToNode

 

IgniteFuture

 

Several methods were removed with no replacement:

 

  • startTime
  • duration

OptimizedMarshaller

Implementation has been removed from public API and is not expected to be used directly anymore. 

IgniteFuture

Several methods were removed with no replacement:

...

BinaryIdentityResolver

Interface has been removed. Now key hash code and equality is calculated based on content of serialized object. 

EventType

Several event types have been removed due to new Ignite page memory architecture:

...

This change affects multi-platform Ignite applications where Java and .NET types are mapped to each other. More details: https://apacheignite-net.readme.io/docs/platform-interoperability

 

Schema import utility - ?

...