Apache Ignite 2.7.6 released, Ignite is a memory-centric distributed to HTAP database, caching and processing platforms, support services, analysis and streaming load, you can enjoy the memory-class performance on the PB-level data.
This is a small version of the update, mainly to solve the following problems:
Ignite:
- When IGNITE_HOME not configured, adjust the default directory persistence, persistence native files are no longer stored in the temporary directory;
- Repair performed using the equations on the part of the primary key of the composite SELECT query predicate, even if a plurality of lines will match the return of a single row of data;
- Fixed an issue during the execution of the checkpoint may cause data corruption;
- Fixed group shared cache line size calculation error, resulting in the problem tree damage;
- To reduce the Java heap footprint by optimizing GridDhtPartitionsFullMessage mapping in exchange history;
- Fixed holding destroyed a cache of outdated cluster node failure causes problems;
- After the repair of the existing indexes and delete other values reconstruction, the problem can not change the existing indexes inline_size property;
- Repair could cause problems control.sh script can not be executed when JAVA_HOME is not set;
- Fixed opens the problem may be caused when a node failure persistence and disable WAL MMAP;
- Fixed an issue where killed in checkpoint marking phase node may result in damage to the PDS;
Ignite .NET:
- Native persistence can now use a custom mapping function;
- Fixed CacheEntryEventType.Removed event missing.