This is an automated email from the ASF dual-hosted git repository.
ctargett pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/solr.git
The following commit(s) were added to refs/heads/main by this push:
new caf8cbc Ref Guide: fix bad link and list item out of order
caf8cbc is described below
commit caf8cbc0aa11e32f894a90531e3e9f20edf75efa
Author: Cassandra Targett <[email protected]>
AuthorDate: Wed Mar 31 13:16:04 2021 -0500
Ref Guide: fix bad link and list item out of order
---
solr/solr-ref-guide/src/de-duplication.adoc | 5 ++---
solr/solr-ref-guide/src/solr-control-script-reference.adoc | 2 +-
2 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/solr/solr-ref-guide/src/de-duplication.adoc
b/solr/solr-ref-guide/src/de-duplication.adoc
index cb12bca..c7918bf 100644
--- a/solr/solr-ref-guide/src/de-duplication.adoc
+++ b/solr/solr-ref-guide/src/de-duplication.adoc
@@ -84,9 +84,8 @@ If *true*, the default, when a document exists that already
matches this signatu
There are 2 important things to keep in mind when using
`SignatureUpdateProcessorFactory` with SolrCloud:
-1. The `overwriteDupes=true` setting does not work _except_ in the special
case of using the uniqueKey field as the `signatureField`. Attempting
De-duplication on any other `signatureField` will not work correctly because of
how updates are forwarded to replicas
-1. When using the uniqueKey field as the `signatureField`,
`SignatureUpdateProcessorFactory` must be run prior to the
`<<update-request-processors.adoc#update-processors-in-solrcloud,DistributedUpdateProcessor>>`
to ensure that documents can be routed to the correct shard leader based on
the (generated) uniqueKey field.
+. The `overwriteDupes=true` setting does not work _except_ in the special case
of using the uniqueKey field as the `signatureField`. Attempting
De-duplication on any other `signatureField` will not work correctly because of
how updates are forwarded to replicas
+. When using the uniqueKey field as the `signatureField`,
`SignatureUpdateProcessorFactory` must be run prior to the
`<<update-request-processors.adoc#update-processors-in-solrcloud,DistributedUpdateProcessor>>`
to ensure that documents can be routed to the correct shard leader based on
the (generated) uniqueKey field.
(Using any other `signatureField` with `overwriteDupes=false` -- to generate a
Signature for each document with out De-duplication -- has no limitations.)
====
-
diff --git a/solr/solr-ref-guide/src/solr-control-script-reference.adoc
b/solr/solr-ref-guide/src/solr-control-script-reference.adoc
index 499d74e..15dda4f 100644
--- a/solr/solr-ref-guide/src/solr-control-script-reference.adoc
+++ b/solr/solr-ref-guide/src/solr-control-script-reference.adoc
@@ -916,7 +916,7 @@ bin/solr export -url
http://localhost:8983/solr/gettingstarted -1 -out 1MDocs.js
=== Importing Documents to a Collection
-Once you have exported documents in a file, you can use the
<<updatehandlers-in-solrconfig.adoc#,/update request handler>> to import them
to a new Solr collection.
+Once you have exported documents in a file, you can use the
<<uploading-data-with-index-handlers.adoc#,/update request handler>> to import
them to a new Solr collection.
*Example: import `jsonl` files*
