From e9e2ff9b12d4934337aaf757539fba1a3015b387 Mon Sep 17 00:00:00 2001 From: Cassandra Targett Date: Mon, 13 Jul 2020 09:27:01 -0500 Subject: [PATCH] Ref Guide: fix aliases.adoc TIP for proper conversion --- solr/solr-ref-guide/src/aliases.adoc | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/solr/solr-ref-guide/src/aliases.adoc b/solr/solr-ref-guide/src/aliases.adoc index 2bc268a8d42..8b2c0a6a75c 100644 --- a/solr/solr-ref-guide/src/aliases.adoc +++ b/solr/solr-ref-guide/src/aliases.adoc @@ -46,15 +46,18 @@ Alternatively this information is available by checking `/aliases.json` in ZooKe Aliases may be deleted via the <> command. When deleting an alias, underlying collections are *unaffected*. -TIP: Any alias (standard or routed) that references multiple collections may complicate relevancy. +[TIP] +==== +Any alias (standard or routed) that references multiple collections may complicate relevancy. By default, SolrCloud scores documents on a per-shard basis. -+ + With multiple collections in an alias this is always a problem, so if you have a use case for which BM25 or TF/IDF relevancy is important you will want to turn on one of the <> implementations. -+ + However, for analytical use cases where results are sorted on numeric, date, or alphanumeric field values, rather than relevancy calculations, this is not a problem. +==== == Routed Aliases