tm-ms
tm-ms
Developing support technologies like JRebel (#26) or Quarkus (Ticket #J505) use "hot code replacement", i.e. change classes of a live Java process at runtime. This causes MicroStream to fail since...
Before microstream-one/microstream-private#111, a "switchByteOrder" flag had to be passed around at a lot of places to handle translation between the two byte orders. Now, with the MemoryAccessor interface, it might...
Currently, every exception encountered on the storage-level (loading and storing entity data etc.) causes the storage channel threads to cease working. This is intentional to immediately disable any more changes...
The user-defineable refactoring mapping is intended to specify new identifiers for types, fields, constants for vanished old ones (e.g. because of type renaming). However, it can currently also be used...
To translate values from a legacy type instance to a current type instance, value translators with arbitrary logic can be defined. However, for newly added fields, no comparable logic can...
So far, a mechanism is still missing to create the complete definitive TypeDictionary for using MicroStream as a means for communication. Currently, in the proof-of-concept example, the TypeDictionary is defined...
When using MicroStream as a database solution, the use case is virtually completely that if internally managed data. Meaning all parts of the process can be trusted. Hence, no encyption...
There is a dedicated type "StorageFileReader" that is meant to encapsulate all reading from Storage files. E.g. to add logging aspects or replace it by another reading algorithm. However, it...
If the head file is still pretty tiny (e.g. 2 kB with a 8 MB max file size) but already contains a lot of logical gaps (e.g. the same collection...
Deletion in MicroStream works in a very indirect, typical garbage-collected-graph way: There is no actual deletion, only instances becoming unreachable in the graph. This is enough to make them unaccessible...