Hi everyone!
Ignite has a way to limit the amount of memory available to store information.
If this limit is reached, then page eviction or page replacement will kick in
and make sure that the amount occupied space stays in the configured limits.
There are no such settings for the disk storage
l and should stay.
>
> [1] https://github.com/apache/ignite/pull/8221
>
>> 18 дек. 2020 г., в 12:06, Mekhanikov Denis
написал(а):
>>
>> Hi everyone!
>>
>> Ignite has a limitation that it can’t work with custom classes put into
metasto
Hi everyone!
Ignite has a limitation that it can’t work with custom classes put into
metastorage: https://issues.apache.org/jira/browse/IGNITE-13642
If you put a POJO into the metastorage, then Ignite will try to deserialize it
using the classes it finds on the classpath. If it can’t do the
-1 Prohibit.
@deprecated annotation normally means that the method or class or whatever is
not recommended to use, since a new proper implementation is available, and
people should use it instead.
But with @IgniteExperimental this is not the case.
Denis
On 10/02/2020, 11:45, "Юрий" wrote:
