Skip to content

Commit 7607ba7

Browse files
committed
[DOCS] Update ES glossary reference
1 parent d388871 commit 7607ba7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/src/reference/asciidoc/core/arch.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ NOTE: Due to the similarity in concepts, through-out the docs one can think inte
3131

3232
Shards play a critical role when reading information from {es}. Since it acts as a source, {eh} will create one Hadoop `InputSplit` per {es} shard, or in case of {sp} one `Partition`, that is given a query that works against index `I`. {eh} will dynamically discover the number of shards backing `I` and then for each shard will create, in case of Hadoop an input split (which will determine the maximum number of Hadoop tasks to be executed) or in case of Spark a partition which will determine the `RDD` maximum parallelism.
3333

34-
With the default settings, {es} uses *5* {ref}/glossary.html#glossary-primary-shard[`primary`] shards per index which will result in the same number of tasks on the Hadoop side for each query.
34+
With the default settings, {es} uses *5* {glossary}/terms.html#glossary-primary-shard[`primary`] shards per index which will result in the same number of tasks on the Hadoop side for each query.
3535

3636
NOTE: {eh} does not query the same shards - it iterates through all of them (primaries and replicas) using a round-robin approach. To avoid data duplication, only one shard is used from each shard group (primary and replicas).
3737

0 commit comments

Comments
 (0)