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
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
Folks,
This is a friendly reminder :-)
PR [1] is ready for review. Will anyone take a look?
[1] https://github.com/apache/ignite/pull/9577/files
On Sat, 20 Nov 2021 at 03:17, Maxim Muzafarov wrote:
>
> Folks,
>
>
> I've prepared the changes related to the legacy Service Grid removal
> for the
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
Hello,
I want to include the issue [1] to the 2.12 scope. It fixes some
metrics according to the JSR107.
Any objections?
[1] https://issues.apache.org/jira/browse/IGNITE-16002 The remove
cache method should update statistics if the method returns true
чт, 25 нояб. 2021 г. в 17:12, Nikita
