ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philipp Masharov <masharov...@gmail.com>
Subject Re: [DISCUSSION] control.sh argument to enable experimental commands
Date Mon, 07 Sep 2020 10:03:18 GMT
I will try it. Including information about experimental commands into
documentation sounds like a good idea. Am I need to create a Jira ticket?
Definitely I need to follow some process to enhance the product
documentation.

On Mon, Sep 7, 2020 at 12:42 PM Nikolay Izhikov <nizhikov@apache.org> wrote:

> Hello, Philipp.
>
> Indeed, lack of the information about experimental control.sh command is a
> gap in Ignite documentation.
> Do you want to contribute corresponding page to close this gap?
>
> To see all experimental commands you can build Ignite from sources and
> execute the following commands
>
> >> $ export IGNITE_ENABLE_EXPERIMENTAL_COMMAND="true"
> >> $ ./bin/control.sh
>
> > 7 сент. 2020 г., в 12:26, Philipp Masharov <masharov.fv@gmail.com>
> написал(а):
> >
> > Hello Nikolay!
> >
> > It's more convenient to use an option instead of an environmental
> variable.
> > But what is experiment commands? Are these commands not
> production-ready? I
> > never heard about it and I can't find information about experiment
> commands
> > in the product documentation.
> >
> > On Mon, Sep 7, 2020 at 12:08 PM Nikolay Izhikov <nizhikov@apache.org>
> wrote:
> >
> >> Hello, Igniters.
> >>
> >> For now, experimental commands in control.sh can be enabled only via
> >> system property
> >>
> >> ```
> >> $ export IGNITE_ENABLE_EXPERIMENTAL_COMMAND="true"
> >> $ ./bin/control.sh
> >> ```
> >>
> >> I think we should add explicit argument for this.
> >>
> >> ```
> >> ./control.sh —enable-experimental
> >> ```
> >>
> >> WDYT?
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message