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 name or by type identifier):
control.(sh|bat) --meta details [--typeId <typeId>] [--typeName
<typeName>]
Remove the metadata of the specified type (the type must be specified by
type name or by type identifier) from cluster and saves the removed
metadata to the specified file.
If the file name isn't specified the output file name is: '<typeId>.bin'
control.(sh|bat) --meta remove [--typeId <typeId>] [--typeName
<typeName>] [--out <fileName>]
Update cluster metadata from specified file (file name is required)
control.(sh|bat) --meta update --in <fileName>
________
Print tracing configuration:
control.(sh|bat) --tracing-configuration
Print tracing configuration:
control.(sh|bat) --tracing-configuration get_all [--scope
DISCOVERY|EXCHANGE|COMMUNICATION|TX]
Print specific tracing configuration based on specified --scope and
--label:
control.(sh|bat) --tracing-configuration get (--scope
DISCOVERY|EXCHANGE|COMMUNICATION|TX) [--label]
Reset all specific tracing configuration the to default. If --scope is
specified, then remove all label specific configuration for the given scope
and reset given scope specific configuration to the default, if --scope is
skipped then reset all tracing configurations to the default. Print tracing
configuration.
control.(sh|bat) --tracing-configuration reset_all [--scope
DISCOVERY|EXCHANGE|COMMUNICATION|TX]
Reset specific tracing configuration to the default. If both --scope and
--label are specified then remove given configuration, if only --scope is
specified then reset given configuration to the default. Print reseted
configuration.
control.(sh|bat) --tracing-configuration reset (--scope
DISCOVERY|EXCHANGE|COMMUNICATION|TX) [--label]
Set new tracing configuration. If both --scope and --label are specified
then add or override label specific configuration, if only --scope is
specified, then override scope specific configuration. Print applied
configuration.
control.(sh|bat) --tracing-configuration set (--scope
DISCOVERY|EXCHANGE|COMMUNICATION|TX [--label] [--sampling-rate Decimal
value between 0 and 1, where 0 means never and 1 means always. More or less
reflects the probability of sampling specific trace.] [--included-scopes
Set of scopes with comma as separator DISCOVERY|EXCHANGE|COMMUNICATION|TX])
On Mon, Sep 7, 2020 at 1:44 PM Nikolay Izhikov <[email protected]> wrote:
> 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 <[email protected]>
> написал(а):
> >
> > 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, ткаленко кирилл <[email protected]>
> написал(а):
> >>
> >> 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" <[email protected]>:
> >>> 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 <[email protected]>
> 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 <[email protected]>
> >>>> написал(а):
> >>>>>
> >>>>> 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 <[email protected]
> >
> >>>> 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?
> >
>
>
