Merged to master.
> 6 июня 2023 г., в 16:19, Nikolay Izhikov написал(а):
>
> Hello, Igniters.
>
> Last couple of weeks we actively worked on Phase 1 of IEP-81.
> Now, after several dozens of feature branch reviews Phase 1 is almost ready.
>
> If you are interested in new Management API, please
Hello, Igniters.
Last couple of weeks we actively worked on Phase 1 of IEP-81.
Now, after several dozens of feature branch reviews Phase 1 is almost ready.
If you are interested in new Management API, please, join to the reivew.
PR - https://github.com/apache/ignite/pull/10675
IEP -
https://cwi
Hi Maxim,
I like the idea, the IEP looks very useful.
However, I agree with Nikolay on this
>
> Don’t think we should rely on auto scan class path capabilities.
> 1. How this automatic scanner will distinguish ignite class from
> user class if they both in node class path and same packag
Hello, Maxim.
Thanks for the IEP.
I support the intentions and design of the IEP in general but have some
comments:
> AnnotationCommandScanner, PackageCommandScanner, URICommandScanner
Don’t think we should rely on auto scan class path capabilities.
1. How this automatic scanner will di
Igniters,
I'd like to propose a new internal cluster management API that will
simplify new cluster management commands creation and expose new
commands to CLI, REST, JMX Ignite interfaces without any additional
actions from the engineer adding a new command. This main goal of the
IEP is supposed
