1.3.0
This release offers Service Provider Interface for I/O customization in the package jetbrains.exodus.io
. In addition to default disk-based I/O, it lets you configure your application to use an in-memory database, or to access in read-only mode disk-based database opened in another JVM. You can also create your own I/O provider, e.g., for storing data in a remote/cloud file system.
New versioning scheme
Since this release, versioning is changed in order to satisfy development requirements @Jetbrains. Patch numbers no longer will be successive. E.g., next released version definitely won't be 1.3.1
. Apart from that, the new versioning scheme respects all requirements of Semantic Versioning.
Updates of dependencies
Kotlin 1.3.10.
Bug fixes
-
Environments
- #18 — File descriptors leaking issue fix (thanks to Valery Vlasov)
- XD-728 — Log recovery procedure can false negatively diagnose the database is encrypted with unknown cipher parameters in case of recoverable data corruption
- XD-733 — After an OutOfDiskSpaceException, recovery procedure can require application restart
- XD-738 — Utilization profile can get invalid even if there were no cold restarts
- XD-739 — Utilization computed from scratch can be highly inconsistent
- XD-763 — Xodus corrupts data store upon no space left on device
-
Entity Stores
- XD-730 — FilterLinksIterable doesn't work with multiple links
- XD-736 — EntityIterable handle for SortIterable ignores stability flag
- XD-737 — Invalidation of cached FilterLinksIterable is broken if target EntityIterable is constructed as a query using links
- XD-746 — Reversing iterable with entities may throw an exception
- XD-749 — findLinks fails on empty EntityIterableBase
Performance improvements
- Environments