Hello, Kirill. What do you mean by «just open»?
> 7 сент. 2020 г., в 13:22, ткаленко кирилл <tkalkir...@yandex.ru> написал(а): > > Hi, Nikolay! > > It seems that you shouldn't just open experimental commands, that's why they > are experimental. > > > 07.09.2020, 13:03, "Philipp Masharov" <masharov...@gmail.com>: >> 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 <nizhi...@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...@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 <nizhi...@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?
