Page History

...

• IgniteConfiguration's `getGridName/setGridName` methods are deprecated and will be removed in later releases. Use IgniteConfiguration's `getIgniteInstanceName/setIgniteInstanceName` instead.
  
  

• Service Grid calls are processed in a separated Service Grid thread pool which size can be tweaked over `IgniteConfiguration.setServiceThreadPoolSize(...)` method. Before that, the public thread pool served that purpose.
  
  
• Apache Ignite data streamer's calls are going to and processed by a dedicated data streamer's thread pool which size can be tweaked over `IgniteConfiguration.setDataStreamerThreadPoolSize(...)` method. Before that, the public thread pool served that purpose.
  
  
• SQL, Scan and SPI queries are now processed and executed using Threads from Queries thread pool size that is configurable via `IgniteConfiguration.setQueryThreadPoolSize(...)` method. Before that, the system thread pool was used for that purpose.
  
  

Binary Marshalling

• There were several changes in the binary marshalling protocol that make it incompatible with previous Apache Ignite versions.
• `BinaryIdentityResolver` is no longer supported.

Networking

• Confusing `TcpDiscoverySPI.getHeartbeatFrequency` parameter is no longer supported. The parameter used to define a frequency of cluster and cache metrics that are sent by cluster nodes from one to another. Now the frequency can be adjusted with `IgniteConfiguration.setMetricsUpdateFrequency(...)` method.
  
  
• `TcpDiscoveryS3IpFinder.setAwsCredentials(AWSCredentialsProvider)` renamed to `TcpDiscoveryS3IpFinder.setAwsCredentialsProvider(AWSCredentialsProvider)`.
  
  
• Apache Ignite client nodes' failure detection timeout is now set with `IgniteConfiguration.setClientFailureDetectionTimeout(...)` and equal to 30 seconds be default. `IgniteConfiguration.getFailureDetectionTimeout()`, that is equal to 7 seconds, was used as the timeout for both server and client nodes in prior versions.

...

Apache Ignite 2.0 integrates with Hibernate 5.0. The previous integration with a legacy Hibernate version of 4.2 can be used by importing `ignite-hibernate_4.2` Maven artifact or taking a respective JAR file from Apache Ignite 2.0 or later distribution.

Refer to this documentation for more details: https://apacheignite-mix.readme.io/docs/hibernate-l2-cache

Spring Framework

Spring Framework used by several Apache Ignite components has been upgraded to version 4.3.7.RELEASE.