From 8389b87e39e72feb1262ff994d57217f1d127cc8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20H=C3=B8ydahl?= Date: Wed, 19 Feb 2020 10:33:26 +0100 Subject: [PATCH] LUCENE-9229: Fix some broken links Change some wiki -> cwiki links MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Jan Høydahl --- solr/CHANGES.txt | 10 +++++----- solr/solr-ref-guide/src/faceting.adoc | 2 +- solr/solr-ref-guide/src/jvm-settings.adoc | 2 +- solr/solr-ref-guide/src/response-writers.adoc | 2 +- .../src/updating-parts-of-documents.adoc | 2 +- 5 files changed, 9 insertions(+), 9 deletions(-) diff --git a/solr/CHANGES.txt b/solr/CHANGES.txt index 523cec5c7c2..be94a88e6b4 100644 --- a/solr/CHANGES.txt +++ b/solr/CHANGES.txt @@ -11332,7 +11332,7 @@ Upgrading from Solr 4.7 Oracle Java 7 or OpenJDK 7, be sure to not use the GA build 147 or update versions u40, u45 and u51! We recommend using u55 or later. An overview of known JVM bugs can be found on - http://wiki.apache.org/lucene-java/JavaBugs + https://cwiki.apache.org/confluence/display/lucene/JavaBugs * ZooKeeper is upgraded from 3.4.5 to 3.4.6. @@ -14644,7 +14644,7 @@ Other Changes in the migration of existing clients. (yonik) * SOLR-3691: SimplePostTool: Mode for crawling/posting web pages - See http://wiki.apache.org/solr/ExtractingRequestHandler for examples (janhoy) + See https://lucene.apache.org/solr/guide/post-tool.html for examples (janhoy) * SOLR-3707: Upgrade Solr to Tika 1.2 (janhoy) @@ -14774,7 +14774,7 @@ New Features same name. (hossman, steffkes) * SOLR-1280: Added commented-out example of the new script update processor - to the example configuration. See http://wiki.apache.org/solr/ScriptUpdateProcessor (ehatcher) + to the example configuration. (ehatcher) * SOLR-3672: SimplePostTool: Improvements for posting files Support for auto mode, recursive and wildcards (janhoy) @@ -14913,7 +14913,7 @@ Other Changes ================== 4.0.0-ALPHA ================== More information about this release, including any errata related to the release notes, upgrade instructions, or other changes may be found online at: - https://wiki.apache.org/solr/Solr4.0 + https://cwiki.apache.org/confluence/display/solr/Solr4.0 Versions of Major Components @@ -16738,7 +16738,7 @@ New Features Great Circle (haversine), Manhattan, Euclidean and String (using the StringDistance methods in the Lucene spellchecker). Also added geohash(), deg() and rad() convenience functions. - See http://wiki.apache.org/solr/FunctionQuery. (gsingers) + See https://lucene.apache.org/solr/guide/function-queries.html (gsingers) * SOLR-1553: New dismax parser implementation (accessible as "edismax") that supports full lucene syntax, improved reserved char escaping, diff --git a/solr/solr-ref-guide/src/faceting.adoc b/solr/solr-ref-guide/src/faceting.adoc index 54731172c95..dd0eafaf781 100644 --- a/solr/solr-ref-guide/src/faceting.adoc +++ b/solr/solr-ref-guide/src/faceting.adoc @@ -584,7 +584,7 @@ Consider the following example query with faceting: Because everything is already constrained by the filter `doctype:pdf`, the `facet.field=doctype` facet command is currently redundant and will return 0 counts for everything except `doctype:pdf`. -To implement a multi-select facet for doctype, a GUI may want to still display the other doctype values and their associated counts, as if the http://doctypepdf[`doctype:pdf`] constraint had not yet been applied. For example: +To implement a multi-select facet for doctype, a GUI may want to still display the other doctype values and their associated counts, as if the `doctype:pdf` constraint had not yet been applied. For example: [source,text] ---- diff --git a/solr/solr-ref-guide/src/jvm-settings.adoc b/solr/solr-ref-guide/src/jvm-settings.adoc index 97a98c957a8..99aa655fbdc 100644 --- a/solr/solr-ref-guide/src/jvm-settings.adoc +++ b/solr/solr-ref-guide/src/jvm-settings.adoc @@ -35,7 +35,7 @@ There are several points to keep in mind: * The heap allocated should be as small as possible while maintaining good performance. 8-16G is quite common, and larger heaps are sometimes used. When heaps grow to larger sizes, it is imperative to test extensively before going to production. * The G1GC garbage collector is currently preferred when using a JVM that supports it (Java 9 and later) * Modern hardware can be configured with hundreds of gigabytes of physical RAM and many CPUs. It is often better in these cases to run multiple JVMs, each with a limited amount of memory allocated to their heaps. - * It's good practice to periodically re-analyze the GC logs and/or monitor with <> to see if the memory usage has changed due to changes in your application, number of documents, etc. + * It's good practice to periodically re-analyze the GC logs and/or monitor with <> to see if the memory usage has changed due to changes in your application, number of documents, etc. * On *nix systems, we recommend that Solr be run with the "oom killer script" (see solr/bin/oom_solr.sh). This will forcefully stop Solr when the heap is exhausted rather than continue in an indeterminate state. * All current (Java 11) garbage collectors can hit "stop the world" collections, which suspend the JVM until completed. If, through monitoring, these collections are frequent and greater than your application can tolerate, additional tuning should be considered. "Stop the world" pauses greater than 5 seconds are rarely acceptable, and having them be less than 1 second is desirable. diff --git a/solr/solr-ref-guide/src/response-writers.adoc b/solr/solr-ref-guide/src/response-writers.adoc index 493cdaf3809..a9216583064 100644 --- a/solr/solr-ref-guide/src/response-writers.adoc +++ b/solr/solr-ref-guide/src/response-writers.adoc @@ -307,7 +307,7 @@ See the <