Alexey.

The issue with the existing method.

Single implementation for both Ignite#active(boolean) and 
IgniteMXBean#active(boolean)
Should it continue to silently clears in-memory caches?

> 14 февр. 2020 г., в 15:20, Alexey Goncharuk <alexey.goncha...@gmail.com> 
> написал(а):
> 
> Igniters,
> 
> Do we really need the confirmation flag on the public API? I absolutely
> agree on the CLI and MXBean, but what is the reason for the flag in the
> API? It will be specified at the compile time anyway and does not prevent
> any user error.
> From the implementation point of view I see no contradiction - we can add
> the new method to the MXBean, but nothing forces us to add it to Ignite
> interface - those interfaces are not related.

Reply via email to