diff --git a/docs/reference/modules/cross-cluster-search.asciidoc b/docs/reference/modules/cross-cluster-search.asciidoc index 33a159a184eae..ec62da6cb4a83 100644 --- a/docs/reference/modules/cross-cluster-search.asciidoc +++ b/docs/reference/modules/cross-cluster-search.asciidoc @@ -8,6 +8,17 @@ filter and analyze log data stored on clusters in different data centers. IMPORTANT: {ccs-cap} requires <>. +[float] +[[ccs-supported-apis]] +== Supported APIs + +The following APIs support {ccs}: + +* <> +* <> +* <> +* <> + [float] [[ccs-example]] == {ccs-cap} examples @@ -55,7 +66,7 @@ PUT _cluster/settings [[ccs-search-remote-cluster]] === Search a single remote cluster -The following <> API request searches the +The following <> API request searches the `twitter` index on a single remote cluster, `cluster_one`. [source,console] @@ -284,13 +295,12 @@ including a <> or + See <> to learn how this option works. -<>:: -For search requests that include a scroll or inner hits, {es} sends multiple -outgoing and ingoing requests to each remote cluster. You can also choose this -option by setting the <> API's -<> parameter to `false`. -While typically slower, this approach may work well for networks with low -latency. +<>:: For search +requests that include a scroll or inner hits, {es} sends multiple outgoing and +ingoing requests to each remote cluster. You can also choose this option by +setting the <> parameter to +`false`. While typically slower, this approach may work well for networks with +low latency. + See <> to learn how this option works.