This is an automated email from the ASF dual-hosted git repository. abudnikov pushed a commit to branch IGNITE-7595 in repository https://gitbox.apache.org/repos/asf/ignite.git
commit 02ed896add1e96c48d61e9d6f4aff20f65099a97 Author: abudnikov <[email protected]> AuthorDate: Thu Aug 27 12:57:52 2020 +0300 minor updates --- .../java/src/main/java/org/apache/ignite/snippets/ClusterAPI.java | 2 -- docs/_docs/monitoring-metrics/tracing.adoc | 4 ++-- docs/_docs/plugins.adoc | 4 +--- 3 files changed, 3 insertions(+), 7 deletions(-) diff --git a/docs/_docs/code-snippets/java/src/main/java/org/apache/ignite/snippets/ClusterAPI.java b/docs/_docs/code-snippets/java/src/main/java/org/apache/ignite/snippets/ClusterAPI.java index d56d8a0..552f2a9 100644 --- a/docs/_docs/code-snippets/java/src/main/java/org/apache/ignite/snippets/ClusterAPI.java +++ b/docs/_docs/code-snippets/java/src/main/java/org/apache/ignite/snippets/ClusterAPI.java @@ -1,7 +1,5 @@ package org.apache.ignite.snippets; -import java.util.UUID; - import org.apache.ignite.Ignite; import org.apache.ignite.IgniteCheckedException; import org.apache.ignite.IgniteCluster; diff --git a/docs/_docs/monitoring-metrics/tracing.adoc b/docs/_docs/monitoring-metrics/tracing.adoc index 5db0717..575db00 100644 --- a/docs/_docs/monitoring-metrics/tracing.adoc +++ b/docs/_docs/monitoring-metrics/tracing.adoc @@ -56,8 +56,8 @@ You can do this in two ways: * via the control script from the command line * programmatically -Traces are collected with a given probabilistic sampling rate. -The rate is specified as a value between 0 and 1 inclusive: `0` means no sampling, `1` means always sampling. +Traces are collected at a given probabilistic sampling rate. +The rate is specified as a value between 0.0 and 1.0 inclusive: `0` means no sampling, `1` means always sampling. When the sampling rate is set to a value greater than 0, Ignite collects traces. To disable trace collection, set the sampling rate to 0. diff --git a/docs/_docs/plugins.adoc b/docs/_docs/plugins.adoc index b9d038b..e5d1d30 100644 --- a/docs/_docs/plugins.adoc +++ b/docs/_docs/plugins.adoc @@ -2,8 +2,6 @@ == Overview - - The Ignite plugin system allows you to extend the core functionality of Ignite. Plugins have access to different internal Ignite components, such as security processor and others, and can extend the programmatic API of Ignite. @@ -52,7 +50,6 @@ include::{javaCodeDir}/plugin/MyPluginProvider.java[tags=!no-op-methods, indent= The `onIgniteStart()` method is invoked when Ignite is started. We start the plugin by calling `MyPlugin.start()`, which simply schedules periodic execution of the task that prints cache size information. - === {counter:step}. Implement IgnitePlugin The implementation of the `IgnitePlugin` returned by the plugin provider is available to the users via `Ignite.plugin(String pluginName)`. @@ -109,6 +106,7 @@ When you start the node, you should see the following message in the console: === {counter:step}. Access the Plugin at Runtime You can access the instance of the plugin by calling `Ignite.plugin(pluginName)`. +The `pluginName` argument must be equal to the plugin name returned in `MyPluginProvider.name()`. [source, java] ----
