ignite-mesos?
在 2022/5/13 22:51, Maxim Muzafarov 写道:
Folks,
I've found that the following modules are rarely used and haven't been
change for a few years, but they are released each time Ignite being
released. It seems we can safely move all of them to the Extensions
project.
The list:
-
Hi Misha.
Thank you for your valid points.
I accept your suggestion about "ignite cli config get/set" naming.
As for default commands, I think "clear" and "exit" are only for REPL mode and
I'll add them to the description of the commands. "ignite help" is already
defined there.
> On 13 May
+1
> 13 мая 2022 г., в 17:51, Maxim Muzafarov написал(а):
>
> Folks,
>
> I've found that the following modules are rarely used and haven't been
> change for a few years, but they are released each time Ignite being
> released. It seems we can safely move all of them to the Extensions
>
Folks,
I've found that the following modules are rarely used and haven't been
change for a few years, but they are released each time Ignite being
released. It seems we can safely move all of them to the Extensions
project.
The list:
- ignite-yarn
- ignite-geospatial
- ignite-schedule
WDYT?
Hi Maxim.
Thank you for your comments.
- Yes, the non-interactive mode is supported for all commands except "connect",
"disconnect", "status".
- Benefits of using REST as a communication realization between CLI and Ignite
3 cluster:
1) This approach seems to be the de-facto standard for
Hello, Sasha.
The description looks good to me, only a few comments.
1. I would suggest renaming the CLI configuration command. Currently
"ignite default get" and "ignite default set" look not informative. I
understand that "ignite config" is already used for the Ignite
configuration command and
Hello Aleksanrd,
The description looks good. A few questions below:
- Can the CLI also be run in non-interactive mode to support scripts
execution (like the WildFly it does [1])? Will it be possible though
the REST it used?
- What is the benefits and drawbacks of using REST for this tool? Are
Folks,
I've moved the hibernate modules to the Ignite Extension project,
however, we can't deploy them to the Maven Central since they have the
LGPL dependencies. This is also mentioned in the documentation [1].
Users must build them manually from the sources to use.
Another problem I've faced
+1
On Fri, May 13, 2022 at 12:59 PM Николай Ижиков wrote:
> +1
>
> > 13 мая 2022 г., в 12:53, Maxim Muzafarov написал(а):
> >
> > Dear Community,
> >
> >
> > The release candidates are ready.
> >
> > The ignite-zookeeper-ip-finder and ignite-spring-session haven't been
> > changed since the
+1
> 13 мая 2022 г., в 12:53, Maxim Muzafarov написал(а):
>
> Dear Community,
>
>
> The release candidates are ready.
>
> The ignite-zookeeper-ip-finder and ignite-spring-session haven't been
> changed since the last vote. All the issues mentioned in the previous
> vote related to the
Dear Community,
The release candidates are ready.
The ignite-zookeeper-ip-finder and ignite-spring-session haven't been
changed since the last vote. All the issues mentioned in the previous
vote related to the ignite-spring-data-ext have also fixed.
See the links below.
== Ignite Spring Data
11 matches
Mail list logo
