Hello.
> If we want to make metastore more reliable we should provide some command to
> remove keys from it.
Ticket [1] to provide this feature created.
[1] https://issues.apache.org/jira/browse/IGNITE-13901
> 22 дек. 2020 г., в 17:57, Nikolay Izhikov написал(а):
>
> Hello, Anton.
>
> Thank
Hello, Anton.
Thanks for the answer!
> Only maybe, it makes sense to remove such records (with all history) instead
> of filtering them.
I don’t think we should do this, by default.
Imagine scenario #1:
1. Update the plugin to the next bugged version. Some class that is written to
the metas
> How it differs from the current implementation?
There are no differences in implementation. But according to the original
topic, plugins or other external things can write to metastore their own
classes. I just said that according to current architecture it is not a good
idea to do that becaus
Hello, Anton.
> or use the POJO from the ignite core.
How it differs from the current implementation?
> As I can see you have tests only for one node but what happens if different
> nodes have different filters?
The error will happen.
Please, don’t forget that we are talking about two scenar
Hello everyone,
In my opinion, it is indeed better to limit storing to the metastore by
primitive type(map or list are also possible) or use the POJO from the ignite
core.
As Kirill correctly notice, right now, it is a problem not inside of the
distributed metastore but inside of discovery.
In
Nikolay,
Thanks for your reply!
I encountered a similar case to what you've described in point #1. I used a
private plugin that writes some information to the metastorage.
After that I decided to get rid of that plugin, while the information had
already been written to the metastorage.
Followin
Hello everybody!
If you look at the stackTrace, the error is that deserialized objects are being
sent to listeners.
It may be more correct to send a raw arrays of bytes, and each plugin will be
able to process it if needed.
18.12.2020, 12:18, "Nikolay Izhikov" :
> Hello, Denis.
>
> It’s a know
Hello, Denis.
It’s a known issue for me.
Metastore is a private API, isn’t it?
AFAICU it can occur for two reasons:
* User migrates from custom Ignite fork that has private improvements or
plugins that write to the metastore.
* We have a blocker bug and just remove some internal class that can b
