Hello, Igniters.
Ticket [1] to implement explicit option to enable experimental commands created.
[1] https://issues.apache.org/jira/browse/IGNITE-13422
> 7 сент. 2020 г., в 14:08, Philipp Masharov написал(а):
>
> Nikolay, thanks for mentioning it. I fetched the last changes and got this:
>
Nikolay, thanks for mentioning it. I fetched the last changes and got this:
Print metadata command help:
control.(sh|bat) --meta help
Print list of binary metadata types:
control.(sh|bat) --meta list
Print detailed info about specified binary type (the type must be
specified by type
Philipp, at least, we have tracing and binary meta commands in the master.
Please, take a look at current Ignite sources.
> 7 сент. 2020 г., в 13:34, Nikolay Izhikov написал(а):
>
> What is wrong with that?
>
> We just improve the way user enables experimental commands.
> JVM uses similar
What is wrong with that?
We just improve the way user enables experimental commands.
JVM uses similar approach, please, take a look at
'-XX:+UnlockExperimentalVMOptions’.
> 7 сент. 2020 г., в 13:22, ткаленко кирилл написал(а):
>
> Hi, Nikolay!
>
> It seems that you shouldn't just open
07.09.2020, 13:26, "ткаленко кирилл" :
> Adding option "—enable-experimental".
>
> 07.09.2020, 13:22, "ткаленко кирилл" :
>> 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" :
>>> I
Hello, Kirill.
What do you mean by «just open»?
> 7 сент. 2020 г., в 13:22, ткаленко кирилл написал(а):
>
> 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" :
>> I will try it.
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" :
> I will try it. Including information about experimental commands into
> documentation sounds like a good idea. Am I need to create a Jira
I executed control.sh with the option set to true and set false, made a
diff of control.sh outputs and got this:
Print absolute paths of unused archived wal segments on each node:
control.(sh|bat) --wal print
[consistentId1,consistentId2,,consistentIdN]
Delete unused archived wal
Philipp, thanks for your interest.
You may found useful the following links:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document
Note, right now, we change the way on how we document.
Please, take a look into
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 wrote:
> Hello, Philipp.
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
11 matches
Mail list logo
