Page History

...

• Rename GridFutureAdapter and other Ignite Core classes that misuse "adapter" term.
• Remove AbstractFailureHandler.ignoredFailureTypes: critical failures should be handled, not masked. (There is no ideas about how exactly handle unknown errors. Discussion: http://apache-ignite-developers.2346864.n4.nabble.com/GridDhtInvalidPartitionException-takes-the-cluster-down-td41459.html )
• Make 'pairedConnections' on by default in TcpCommunicationSpi?
• Implement new BinaryObject with field type changes and constant-time access to constant-length fields.
• Rename configuration checkpointFrequency to checkpointInterval (or probably other options used Frequency word but really meaning Interval)
• For all versioned FooBarerV3 classes, etc, remove all previous V2,  versionless classes, make it the only one without V3.
• Replace home-brewed GridFutureAdapter with standard CompletableFuture.
• Restructure future interfaces: IgniteInternalFuture should extend IgniteFuture.
• Support Java9+ Automatic modules ( https://issues.apache.org/jira/browse/IGNITE-11461 ) for all Jars.
• Reorder modules tree:
  • group ignite-spring, ignite-flume- ignite-spar, iginte-camel, ignite-cassandra into ignite/integrations
  • group ignite-dev-utils, ignite-benchmarks, ignite-tools  into ignite/dev-support
  • etc...
• Get rid of words Ignite, Grid in internal classes. Examples: GridFutureAdapter, GridManager, GridProcessor, etc...
• .NET: Target .NET Standard 2.0, discontinue .NET 4.0 support
• Redesign REST protocol. 
• Make most of options are runtime configurable.

To Be Removed List For Discussion

...