Apache
/
lucene
mirror of https://github.com/apache/lucene.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Ref Guide: Remove outdated or invalid links to Solr Wiki; update URL of those that remain

This commit is contained in:
Cassandra Targett 2020-01-27 16:37:43 -06:00
parent b2f51f1941
commit 1a14c67426
27 changed files with 49 additions and 53 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
solr/solr-ref-guide/src/a-quick-overview.adoc
View File

@ -41,4 +41,5 @@ A relatively common scenario is that you have so much data, or so many queries,
For example: "Sharding" is a scaling technique in which a collection is split into multiple logical pieces called "shards" in order to scale up the number of documents in a collection beyond what could physically fit on a single server. Incoming queries are distributed to every shard in the collection, which respond with merged results. Another technique available is to increase the "Replication Factor" of your collection, which allows you to add servers with additional copies of your collection to handle higher concurrent query load by spreading the requests around to multiple machines. Sharding and replication are not mutually exclusive, and together make Solr an extremely powerful and scalable platform. For example: "Sharding" is a scaling technique in which a collection is split into multiple logical pieces called "shards" in order to scale up the number of documents in a collection beyond what could physically fit on a single server. Incoming queries are distributed to every shard in the collection, which respond with merged results. Another technique available is to increase the "Replication Factor" of your collection, which allows you to add servers with additional copies of your collection to handle higher concurrent query load by spreading the requests around to multiple machines. Sharding and replication are not mutually exclusive, and together make Solr an extremely powerful and scalable platform.
Best of all, this talk about high-volume applications is not just hypothetical: some of the famous Internet sites that use Solr today are Macy's, EBay, and Zappo's. For more examples, take a look at https://wiki.apache.org/solr/PublicServers. Best of all, this talk about high-volume applications is not just hypothetical: some of the famous Internet sites that use Solr today are Macy's, EBay, and Zappo's.
For more examples, take a look at https://cwiki.apache.org/confluence/display/solr/PublicServers.

2
solr/solr-ref-guide/src/de-duplication.adoc
View File

@ -22,7 +22,7 @@ Preventing duplicate or near duplicate documents from entering an index or taggi
* MD5Signature: 128-bit hash used for exact duplicate detection. * MD5Signature: 128-bit hash used for exact duplicate detection.
* Lookup3Signature: 64-bit hash used for exact duplicate detection. This is much faster than MD5 and smaller to index. * Lookup3Signature: 64-bit hash used for exact duplicate detection. This is much faster than MD5 and smaller to index.
* http://wiki.apache.org/solr/TextProfileSignature[TextProfileSignature]: Fuzzy hashing implementation from Apache Nutch for near duplicate detection. It's tunable but works best on longer text. * https://cwiki.apache.org/confluence/display/solr/TextProfileSignature[TextProfileSignature]: Fuzzy hashing implementation from Apache Nutch for near duplicate detection. It's tunable but works best on longer text.
Other, more sophisticated algorithms for fuzzy/near hashing can be added later. Other, more sophisticated algorithms for fuzzy/near hashing can be added later.

2
solr/solr-ref-guide/src/filter-descriptions.adoc
View File

@ -86,8 +86,6 @@ Arguments may be passed to tokenizer factories to modify their behavior by setti
The following sections describe the filter factories that are included in this release of Solr. The following sections describe the filter factories that are included in this release of Solr.
For user tips about Solr's filters, see http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters.
== ASCII Folding Filter == ASCII Folding Filter
This filter converts alphabetic, numeric, and symbolic Unicode characters which are not in the Basic Latin Unicode block (the first 127 ASCII characters) to their ASCII equivalents, if one exists. This filter converts characters from the following Unicode blocks: This filter converts alphabetic, numeric, and symbolic Unicode characters which are not in the Basic Latin Unicode block (the first 127 ASCII characters) to their ASCII equivalents, if one exists. This filter converts characters from the following Unicode blocks:

2
solr/solr-ref-guide/src/how-to-contribute.adoc
View File

@ -24,7 +24,7 @@ The Guide is written in simple AsciiDoc-formatted files, and the source lives in
The following sections give an overview of how to work with AsciiDoc-format files, how our documentation is generated, and how to do a Ref Guide release. The following sections give an overview of how to work with AsciiDoc-format files, how our documentation is generated, and how to do a Ref Guide release.
Once you have a patch you'd like to contribute, you can submit it with a JIRA issue, the same as any other patch. See also the Solr wiki section on https://wiki.apache.org/solr/HowToContribute[How To Contribute] for information on submitting patches. Once you have a patch you'd like to contribute, you can submit it with a JIRA issue, the same as any other patch. See also the Solr wiki section on https://cwiki.apache.org/confluence/display/solr/HowToContribute[How To Contribute] for information on submitting patches.
== Working with AsciiDoc Files == Working with AsciiDoc Files
include::meta-docs/asciidoc-syntax.adoc[leveloffset=+2] include::meta-docs/asciidoc-syntax.adoc[leveloffset=+2]

6
solr/solr-ref-guide/src/implicit-requesthandlers.adoc
View File

@ -49,7 +49,7 @@ v2: `api/node/logging` |{solr-javadocs}/solr-core/org/apache/solr/handler/admin/
Luke:: Expose the internal Lucene index. This handler must have a collection name in the path to the endpoint. Luke:: Expose the internal Lucene index. This handler must have a collection name in the path to the endpoint.
+ +
*Documentation*: http://wiki.apache.org/solr/LukeRequestHandler *Documentation*: https://cwiki.apache.org/confluence/display/solr/LukeRequestHandler
+ +
[cols="3*.",frame=none,grid=cols,options="header"] [cols="3*.",frame=none,grid=cols,options="header"]
|=== |===
@ -106,8 +106,6 @@ Segments:: Return info on last commit generation Lucene index segments.
System Settings:: Return server statistics and settings. System Settings:: Return server statistics and settings.
+ +
*Documentation*: https://wiki.apache.org/solr/SystemInformationRequestHandlers#SystemInfoHandler
+
[cols="3*.",frame=none,grid=cols,options="header"] [cols="3*.",frame=none,grid=cols,options="header"]
|=== |===
|API Endpoints |Class & Javadocs |Paramset |API Endpoints |Class & Javadocs |Paramset
@ -145,7 +143,7 @@ This endpoint can also take the collection or core name in the path (`solr/<coll
[horizontal] [horizontal]
Document Analysis:: Return a breakdown of the analysis process of the given document. Document Analysis:: Return a breakdown of the analysis process of the given document.
+ +
*Documentation*: https://wiki.apache.org/solr/AnalysisRequestHandler *Documentation*: https://cwiki.apache.org/confluence/display/solr/AnalysisRequestHandler
+ +
[cols="3*.",frame=none,grid=cols,options="header"] [cols="3*.",frame=none,grid=cols,options="header"]
|=== |===

3
solr/solr-ref-guide/src/index-replication.adoc
View File

@ -159,10 +159,9 @@ The code below shows how to configure a ReplicationHandler on a slave.
<!-- To use compression while transferring the index files. The possible <!-- To use compression while transferring the index files. The possible
values are internal|external. If the value is 'external' make sure values are internal|external. If the value is 'external' make sure
that your master Solr has the settings to honor the accept-encoding header. that your master Solr has the settings to honor the accept-encoding header.
See here for details: http://wiki.apache.org/solr/SolrHttpCompression
If it is 'internal' everything will be taken care of automatically. If it is 'internal' everything will be taken care of automatically.
USE THIS ONLY IF YOUR BANDWIDTH IS LOW. USE THIS ONLY IF YOUR BANDWIDTH IS LOW.
THIS CAN ACTUALLY SLOWDOWN REPLICATION IN A LAN --> THIS CAN ACTUALLY SLOW DOWN REPLICATION IN A LAN -->
<str name="compression">internal</str> <str name="compression">internal</str>
<!-- The following values are used when the slave connects to the master to <!-- The following values are used when the slave connects to the master to

12
solr/solr-ref-guide/src/indexconfig-in-solrconfig.adoc
View File

@ -185,15 +185,15 @@ Many <<Merging Index Segments,Merge Policy>> implementations support `noCFSRatio
The LockFactory options specify the locking implementation to use. The LockFactory options specify the locking implementation to use.
The set of valid lock type options depends on the <<datadir-and-directoryfactory-in-solrconfig.adoc#datadir-and-directoryfactory-in-solrconfig,DirectoryFactory>> you have configured. The values listed below are are supported by `StandardDirectoryFactory` (the default): The set of valid lock type options depends on the <<datadir-and-directoryfactory-in-solrconfig.adoc#datadir-and-directoryfactory-in-solrconfig,DirectoryFactory>> you have configured.
* `native` (default) uses NativeFSLockFactory to specify native OS file locking. If a second Solr process attempts to access the directory, it will fail. Do not use when multiple Solr web applications are attempting to share a single index. The values listed below are are supported by `StandardDirectoryFactory` (the default):
* `simple` uses SimpleFSLockFactory to specify a plain file for locking.
* `single` (expert) uses SingleInstanceLockFactory. Use for special situations of a read-only index directory, or when there is no possibility of more than one process trying to modify the index (even sequentially). This type will protect against multiple cores within the _same_ JVM attempting to access the same index. WARNING! If multiple Solr instances in different JVMs modify an index, this type will _not_ protect against index corruption. * `native` (default) uses NativeFSLockFactory to specify native OS file locking. If a second Solr process attempts to access the directory, it will fail. Do not use when multiple Solr web applications are attempting to share a single index. See also the {lucene-javadocs}core/org/apache/lucene/store/NativeFSLockFactory.html[Javadocs].
* `simple` uses SimpleFSLockFactory to specify a plain file for locking. See also the {lucene-javadocs}core/org/apache/lucene/store/SimpleFSLockFactory.html[Javadocs].
* `single` (expert) uses SingleInstanceLockFactory. Use for special situations of a read-only index directory, or when there is no possibility of more than one process trying to modify the index (even sequentially). This type will protect against multiple cores within the _same_ JVM attempting to access the same index. WARNING! If multiple Solr instances in different JVMs modify an index, this type will _not_ protect against index corruption. See also the {lucene-javadocs}core/org/apache/lucene/store/SingleInstanceLockFactory.html[Javadocs].
* `hdfs` uses HdfsLockFactory to support reading and writing index and transaction log files to a HDFS filesystem. See the section <<running-solr-on-hdfs.adoc#running-solr-on-hdfs,Running Solr on HDFS>> for more details on using this feature. * `hdfs` uses HdfsLockFactory to support reading and writing index and transaction log files to a HDFS filesystem. See the section <<running-solr-on-hdfs.adoc#running-solr-on-hdfs,Running Solr on HDFS>> for more details on using this feature.
For more information on the nuances of each LockFactory, see http://wiki.apache.org/lucene-java/AvailableLockFactories.
[source,xml] [source,xml]
---- ----
<lockType>native</lockType> <lockType>native</lockType>

2
solr/solr-ref-guide/src/introduction-to-solr-indexing.adoc
View File

@ -34,8 +34,6 @@ Regardless of the method used to ingest data, there is a common basic data struc
If the field name is defined in the Schema that is associated with the index, then the analysis steps associated with that field will be applied to its content when the content is tokenized. Fields that are not explicitly defined in the Schema will either be ignored or mapped to a dynamic field definition (see <<documents-fields-and-schema-design.adoc#documents-fields-and-schema-design,Documents, Fields, and Schema Design>>), if one matching the field name exists. If the field name is defined in the Schema that is associated with the index, then the analysis steps associated with that field will be applied to its content when the content is tokenized. Fields that are not explicitly defined in the Schema will either be ignored or mapped to a dynamic field definition (see <<documents-fields-and-schema-design.adoc#documents-fields-and-schema-design,Documents, Fields, and Schema Design>>), if one matching the field name exists.
For more information on indexing in Solr, see the https://wiki.apache.org/solr/FrontPage[Solr Wiki].
== The Solr Example Directory == The Solr Example Directory
When starting Solr with the "-e" option, the `example/` directory will be used as base directory for the example Solr instances that are created. This directory also includes an `example/exampledocs/` subdirectory containing sample documents in a variety of formats that you can use to experiment with indexing into the various examples. When starting Solr with the "-e" option, the `example/` directory will be used as base directory for the example Solr instances that are created. This directory also includes an `example/exampledocs/` subdirectory containing sample documents in a variety of formats that you can use to experiment with indexing into the various examples.

2
solr/solr-ref-guide/src/jvm-settings.adoc
View File

@ -20,7 +20,7 @@ Optimizing the JVM can be a key factor in getting the most from your Solr instal
Configuring your JVM can be a complex topic and a full discussion is beyond the scope of this document. Luckily, most modern JVMs are quite good at making the best use of available resources with default settings. The following sections contain a few tips that may be helpful when the defaults are not optimal for your situation. Configuring your JVM can be a complex topic and a full discussion is beyond the scope of this document. Luckily, most modern JVMs are quite good at making the best use of available resources with default settings. The following sections contain a few tips that may be helpful when the defaults are not optimal for your situation.
For more general information about improving Solr performance, see https://wiki.apache.org/solr/SolrPerformanceFactors. For more general information about improving Solr performance, see https://cwiki.apache.org/confluence/display/solr/SolrPerformanceFactors[Solr Performance Factors] in the Solr Wiki.
== Choosing Memory Heap Settings == Choosing Memory Heap Settings

12
solr/solr-ref-guide/src/language-analysis.adoc
View File

@ -887,10 +887,10 @@ There are two filters written specifically for dealing with Bengali language. Th
[.tab-label]*With class name (legacy)* [.tab-label]*With class name (legacy)*
[source,xml] [source,xml]
---- ----
<analyzer> <analyzer>
<tokenizer class="solr.StandardTokenizerFactory"/> <tokenizer class="solr.StandardTokenizerFactory"/>
<filter class="solr.BengaliNormalizationFilterFactory"/> <filter class="solr.BengaliNormalizationFilterFactory"/>
<filter class="solr.BengaliStemFilterFactory"/> <filter class="solr.BengaliStemFilterFactory"/>
</analyzer> </analyzer>
---- ----
==== ====
@ -898,7 +898,7 @@ There are two filters written specifically for dealing with Bengali language. Th
*Normalisation* - `মানুষ` \-> `মানুস` *Normalisation* - `মানুষ` \-> `মানুস`
*Stemming* - `সমস্ত` \-> `সমস্` *Stemming* - `সমস্ত` \-> `সমস্`
=== Brazilian Portuguese === Brazilian Portuguese
@ -2455,7 +2455,7 @@ It's a semantically more destructive solution than `ScandinavianNormalizationFil
Solr includes a filter that normalizes Serbian Cyrillic and Latin characters. Note that this filter only works with lowercased input. Solr includes a filter that normalizes Serbian Cyrillic and Latin characters. Note that this filter only works with lowercased input.
See the Solr wiki for tips & advice on using this filter: https://wiki.apache.org/solr/SerbianLanguageSupport For user tips & advice on using this filter, see https://cwiki.apache.org/confluence/display/solr/SerbianLanguageSupport[Serbian Language Support] in the Solr Wiki.
*Factory class:* `solr.SerbianNormalizationFilterFactory` *Factory class:* `solr.SerbianNormalizationFilterFactory`

4
solr/solr-ref-guide/src/learning-to-rank.adoc
View File

@ -451,8 +451,8 @@ Contributions for further models, features and normalizers are welcome. Related
* {solr-javadocs}/solr-ltr/org/apache/solr/ltr/model/LTRScoringModel.html[LTRScoringModel javadocs] * {solr-javadocs}/solr-ltr/org/apache/solr/ltr/model/LTRScoringModel.html[LTRScoringModel javadocs]
* {solr-javadocs}/solr-ltr/org/apache/solr/ltr/feature/Feature.html[Feature javadocs] * {solr-javadocs}/solr-ltr/org/apache/solr/ltr/feature/Feature.html[Feature javadocs]
* {solr-javadocs}/solr-ltr/org/apache/solr/ltr/norm/Normalizer.html[Normalizer javadocs] * {solr-javadocs}/solr-ltr/org/apache/solr/ltr/norm/Normalizer.html[Normalizer javadocs]
* http://wiki.apache.org/solr/HowToContribute * https://cwiki.apache.org/confluence/display/solr/HowToContribute
* http://wiki.apache.org/lucene-java/HowToContribute * https://cwiki.apache.org/confluence/display/LUCENE/HowToContribute
== LTR Lifecycle == LTR Lifecycle

14
solr/solr-ref-guide/src/major-changes-in-solr-8.adoc
View File

@ -272,7 +272,7 @@ Please be sure to review this list so you understand what may have changed betwe
=== Solr 7.7 === Solr 7.7
See the https://wiki.apache.org/solr/ReleaseNote77[7.7 Release Notes] for an overview of the main new features in Solr 7.7. See the https://cwiki.apache.org/confluence/display/solr/ReleaseNote77[7.7 Release Notes] for an overview of the main new features in Solr 7.7.
When upgrading to Solr 7.7.x, users should be aware of the following major changes from v7.6: When upgrading to Solr 7.7.x, users should be aware of the following major changes from v7.6:
@ -294,7 +294,7 @@ For more information, see the <<distributed-requests.adoc#configuring-the-shardh
=== Solr 7.6 === Solr 7.6
See the https://wiki.apache.org/solr/ReleaseNote76[7.6 Release Notes] for an overview of the main new features in Solr 7.6. See the https://cwiki.apache.org/confluence/display/solr/ReleaseNote76[7.6 Release Notes] for an overview of the main new features in Solr 7.6.
When upgrading to Solr 7.6, users should be aware of the following major changes from v7.5: When upgrading to Solr 7.6, users should be aware of the following major changes from v7.5:
@ -351,7 +351,7 @@ For more information about the directory factory configuration in Solr, see the
=== Solr 7.5 === Solr 7.5
See the https://wiki.apache.org/solr/ReleaseNote75[7.5 Release Notes] for an overview of the main new features in Solr 7.5. See the https://cwiki.apache.org/confluence/display/solr/ReleaseNote75[7.5 Release Notes] for an overview of the main new features in Solr 7.5.
When upgrading to Solr 7.5, users should be aware of the following major changes from v7.4: When upgrading to Solr 7.5, users should be aware of the following major changes from v7.4:
@ -381,7 +381,7 @@ The `TieredMergePolicy` will also reclaim resources from segments that exceed `m
=== Solr 7.4 === Solr 7.4
See the https://wiki.apache.org/solr/ReleaseNote74[7.4 Release Notes] for an overview of the main new features in Solr 7.4. See the https://cwiki.apache.org/confluence/display/solr/ReleaseNote74[7.4 Release Notes] for an overview of the main new features in Solr 7.4.
When upgrading to Solr 7.4, users should be aware of the following major changes from v7.3: When upgrading to Solr 7.4, users should be aware of the following major changes from v7.3:
@ -399,7 +399,7 @@ If you are upgrading from a version earlier than Solr 7.3, please see previous v
=== Solr 7.3 === Solr 7.3
See the https://wiki.apache.org/solr/ReleaseNote73[7.3 Release Notes] for an overview of the main new features in Solr 7.3. See the https://cwiki.apache.org/confluence/display/solr/ReleaseNote73[7.3 Release Notes] for an overview of the main new features in Solr 7.3.
When upgrading to Solr 7.3, users should be aware of the following major changes from v7.2: When upgrading to Solr 7.3, users should be aware of the following major changes from v7.2:
@ -443,7 +443,7 @@ If you are upgrading from a version earlier than Solr 7.2, please see previous v
=== Solr 7.2 === Solr 7.2
See the https://wiki.apache.org/solr/ReleaseNote72[7.2 Release Notes] for an overview of the main new features in Solr 7.2. See the https://cwiki.apache.org/confluence/display/solr/ReleaseNote72[7.2 Release Notes] for an overview of the main new features in Solr 7.2.
When upgrading to Solr 7.2, users should be aware of the following major changes from v7.1: When upgrading to Solr 7.2, users should be aware of the following major changes from v7.1:
@ -469,7 +469,7 @@ If you are upgrading from a version earlier than Solr 7.1, please see previous v
=== Solr 7.1 === Solr 7.1
See the https://wiki.apache.org/solr/ReleaseNote71[7.1 Release Notes] for an overview of the main new features of Solr 7.1. See the https://cwiki.apache.org/confluence/display/solr/ReleaseNote71[7.1 Release Notes] for an overview of the main new features of Solr 7.1.
When upgrading to Solr 7.1, users should be aware of the following major changes from v7.0: When upgrading to Solr 7.1, users should be aware of the following major changes from v7.0:

2
solr/solr-ref-guide/src/other-parsers.adoc
View File

@ -663,7 +663,7 @@ node 4: movie_directors_shard1_replica4
At query time, the `JoinQParser` will access the local replica of the *movie_directors* collection to perform the join. If a local replica is not available or active, then the query will fail. At this point, it should be clear that since you're limited to a single shard and the data must be replicated across all nodes where it is needed, this approach works better with smaller data sets where there is a one-to-many relationship between the from collection and the to collection. Moreover, if you add a replica to the to collection, then you also need to add a replica for the from collection. At query time, the `JoinQParser` will access the local replica of the *movie_directors* collection to perform the join. If a local replica is not available or active, then the query will fail. At this point, it should be clear that since you're limited to a single shard and the data must be replicated across all nodes where it is needed, this approach works better with smaller data sets where there is a one-to-many relationship between the from collection and the to collection. Moreover, if you add a replica to the to collection, then you also need to add a replica for the from collection.
For more information about join queries, see the Solr Wiki page on http://wiki.apache.org/solr/Join[Joins]. Erick Erickson has also written a blog post about join performance titled https://lucidworks.com/2012/06/20/solr-and-joins/[Solr and Joins]. For more information, Erick Erickson has written a blog post about join performance titled https://lucidworks.com/2012/06/20/solr-and-joins/[Solr and Joins].
== Lucene Query Parser == Lucene Query Parser

2
solr/solr-ref-guide/src/overview-of-the-solr-admin-ui.adoc
View File

@ -72,7 +72,7 @@ These icons include the following links.
|Documentation |Navigates to the Apache Solr documentation hosted on https://lucene.apache.org/solr/. |Documentation |Navigates to the Apache Solr documentation hosted on https://lucene.apache.org/solr/.
|Issue Tracker |Navigates to the JIRA issue tracking server for the Apache Solr project. This server resides at https://issues.apache.org/jira/browse/SOLR. |Issue Tracker |Navigates to the JIRA issue tracking server for the Apache Solr project. This server resides at https://issues.apache.org/jira/browse/SOLR.
|IRC Channel |Navigates to Solr's http://en.wikipedia.org/wiki/Internet_Relay_Chat[IRC] live-chat room: http://webchat.freenode.net/?channels=#solr. |IRC Channel |Navigates to Solr's http://en.wikipedia.org/wiki/Internet_Relay_Chat[IRC] live-chat room: http://webchat.freenode.net/?channels=#solr.
|Community forum |Navigates to the Apache Wiki page which has further information about ways to engage in the Solr User community mailing lists: https://wiki.apache.org/solr/UsingMailingLists. |Community forum |Navigates to the Apache Wiki page which has further information about ways to engage in the Solr User community mailing lists: https://cwiki.apache.org/confluence/display/solr/UsingMailingLists.
|Solr Query Syntax |Navigates to the section <<query-syntax-and-parsing.adoc#query-syntax-and-parsing,Query Syntax and Parsing>> in this Reference Guide. |Solr Query Syntax |Navigates to the section <<query-syntax-and-parsing.adoc#query-syntax-and-parsing,Query Syntax and Parsing>> in this Reference Guide.
|=== |===

2
solr/solr-ref-guide/src/response-writers.adoc
View File

@ -257,7 +257,7 @@ rsp['response']['docs'].each { |doc| puts 'name field = ' + doc['name'\] }
The CSV response writer returns a list of documents in comma-separated values (CSV) format. Other information that would normally be included in a response, such as facet information, is excluded. The CSV response writer returns a list of documents in comma-separated values (CSV) format. Other information that would normally be included in a response, such as facet information, is excluded.
The CSV response writer supports multi-valued fields, as well as<<transforming-result-documents.adoc#transforming-result-documents,pseudo-fields>>, and the output of this CSV format is compatible with Solr's https://wiki.apache.org/solr/UpdateCSV[CSV update format]. The CSV response writer supports multi-valued fields, as well as <<transforming-result-documents.adoc#transforming-result-documents,pseudo-fields>>, and the output of this CSV format is compatible with Solr's <<uploading-data-with-index-handlers.adoc#csv-formatted-index-updates,CSV update format>>.
=== CSV Parameters === CSV Parameters

2
solr/solr-ref-guide/src/solr-system-requirements.adoc
View File

@ -39,7 +39,7 @@ Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
The exact output will vary, but you need to make sure you meet the minimum version requirement. We also recommend choosing a version that is not end-of-life from its vendor. Oracle/OpenJDK are the most tested JREs and are preferred. It's also preferred to use the latest available official release. The exact output will vary, but you need to make sure you meet the minimum version requirement. We also recommend choosing a version that is not end-of-life from its vendor. Oracle/OpenJDK are the most tested JREs and are preferred. It's also preferred to use the latest available official release.
Some versions of Java VM have bugs that may impact your implementation. To be sure, check the page https://wiki.apache.org/confluence/display/LUCENEJAVA/JavaBugs[Lucene Java Bugs]. Some versions of Java VM have bugs that may impact your implementation. To be sure, check the page https://cwiki.apache.org/confluence/display/LUCENE/JavaBugs[Lucene Java Bugs].
=== Sources for Java === Sources for Java

2
solr/solr-ref-guide/src/solr-upgrade-notes.adoc
View File

@ -226,7 +226,7 @@ This release adds support for tracing requests in Solr. Please review the sectio
=== Solr 8.1 === Solr 8.1
See the https://wiki.apache.org/solr/ReleaseNote810[8.1 Release Notes] for an overview of the main new features of Solr 8.1. See the https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote810[8.1 Release Notes] for an overview of the main new features of Solr 8.1.
When upgrading to 8.1.x, users should be aware of the following major changes from v8.0. When upgrading to 8.1.x, users should be aware of the following major changes from v8.0.

5
solr/solr-ref-guide/src/solrcloud-with-legacy-configuration-files.adoc
View File

@ -42,7 +42,7 @@ These properties exist in 3 files: `schema.xml`, `solrconfig.xml`, and `solr.xml
</updateHandler> </updateHandler>
---- ----
+ +
. The http://wiki.apache.org/solr/UpdateRequestProcessor#Distributed_Updates[DistributedUpdateProcessor] is part of the default update chain and is automatically injected into any of your custom update chains, so you don't actually need to make any changes for this capability. However, should you wish to add it explicitly, you can still add it to the `solrconfig.xml` file as part of an `updateRequestProcessorChain`. For example: . The DistributedUpdateProcessor is part of the default update chain and is automatically injected into any of your custom update chains, so you don't actually need to make any changes for this capability. However, should you wish to add it explicitly, you can still add it to the `solrconfig.xml` file as part of an `updateRequestProcessorChain`. For example:
+ +
[source,xml] [source,xml]
---- ----
@ -67,3 +67,6 @@ If you do not want the DistributedUpdateProcessFactory auto-injected into your c
---- ----
+ +
In the update process, Solr skips updating processors that have already been run on other nodes. In the update process, Solr skips updating processors that have already been run on other nodes.
+
For more on the default update request processor chain and options, see
the section <<update-request-processors.adoc#default-update-request-processor-chain,Default Update Request Processor Chain>>.

4
solr/solr-ref-guide/src/spatial-search.adoc
View File

@ -38,7 +38,7 @@ There are four main field types available for spatial search:
`BBoxField` is for indexing bounding boxes, querying by a box, specifying a search predicate (Intersects,Within,Contains,Disjoint,Equals), and a relevancy sort/boost like overlapRatio or simply the area. `BBoxField` is for indexing bounding boxes, querying by a box, specifying a search predicate (Intersects,Within,Contains,Disjoint,Equals), and a relevancy sort/boost like overlapRatio or simply the area.
Some esoteric details that are not in this guide can be found at http://wiki.apache.org/solr/SpatialSearch. Some esoteric details that are not in this guide can be found in the https://cwiki.apache.org/confluence/display/solr/SpatialSearch[Spatial Search] section of the Solr Wiki.
== LatLonPointSpatialField == LatLonPointSpatialField
@ -334,7 +334,7 @@ Here's an example polygon query for a field "geo" that can be either solr.Spatia
Inside the parenthesis following the search predicate is the shape definition. The format of that shape is governed by the `format` attribute on the field type, defaulting to WKT. If you prefer GeoJSON, you can specify that instead. Inside the parenthesis following the search predicate is the shape definition. The format of that shape is governed by the `format` attribute on the field type, defaulting to WKT. If you prefer GeoJSON, you can specify that instead.
Beyond this Reference Guide and Spatila4j's docs, there are some details that remain at the Solr Wiki at http://wiki.apache.org/solr/SolrAdaptersForLuceneSpatial4. Beyond this Reference Guide and Spatila4j's docs, there are some details that remain at the Solr Wiki at https://cwiki.apache.org/confluence/display/solr/SolrAdaptersForLuceneSpatial4.
=== Geo3D and Polygons (on the ellipsoid) === Geo3D and Polygons (on the ellipsoid)

2
solr/solr-ref-guide/src/taking-solr-to-production.adoc
View File

@ -188,7 +188,7 @@ SOLR_JAVA_MEM="-Xms10g -Xmx10g"
Also, the <<solr-control-script-reference.adoc#solr-control-script-reference,Solr Control Script>> comes with a set of pre-configured Garbage First Garbage Collection settings that have shown to work well with Solr for a number of different workloads. Also, the <<solr-control-script-reference.adoc#solr-control-script-reference,Solr Control Script>> comes with a set of pre-configured Garbage First Garbage Collection settings that have shown to work well with Solr for a number of different workloads.
However, these settings may not work well for your specific use of Solr. Consequently, you may need to change the GC settings, which should also be done with the `GC_TUNE` variable in the `/etc/default/solr.in.sh` include file. For more information about garbage collection settings refer to following articles: However, these settings may not work well for your specific use of Solr. Consequently, you may need to change the GC settings, which should also be done with the `GC_TUNE` variable in the `/etc/default/solr.in.sh` include file. For more information about garbage collection settings refer to following articles:
1. https://wiki.apache.org/solr/ShawnHeisey 1. https://cwiki.apache.org/confluence/display/solr/ShawnHeisey
2. https://www.oracle.com/technetwork/articles/java/g1gc-1984535.html 2. https://www.oracle.com/technetwork/articles/java/g1gc-1984535.html
You can also refer to <<jvm-settings.adoc#jvm-settings,JVM Settings>> for tuning your memory and garbage collection settings. You can also refer to <<jvm-settings.adoc#jvm-settings,JVM Settings>> for tuning your memory and garbage collection settings.

2
solr/solr-ref-guide/src/the-term-vector-component.adoc
View File

@ -160,7 +160,7 @@ If `true`, calculates TF / DF (i.e.,: TF * IDF) for each term. Please note that
+ +
This parameter requires both `tv.tf` and `tv.df` to be "true". This can be computationally expensive. (The results are not shown in example output) This parameter requires both `tv.tf` and `tv.df` to be "true". This can be computationally expensive. (The results are not shown in example output)
To see an example of TermVector component output, see the Wiki page: http://wiki.apache.org/solr/TermVectorComponentExampleOptions To see an example of TermVector component output, see the Wiki page: https://cwiki.apache.org/confluence/display/solr/TermVectorComponentExampleOptions
For schema requirements, see also the section <<field-properties-by-use-case.adoc#field-properties-by-use-case, Field Properties by Use Case>>. For schema requirements, see also the section <<field-properties-by-use-case.adoc#field-properties-by-use-case, Field Properties by Use Case>>.

2
solr/solr-ref-guide/src/tokenizers.adoc
View File

@ -84,8 +84,6 @@ Arguments may be passed to tokenizer factories by setting attributes on the `<to
The following sections describe the tokenizer factory classes included in this release of Solr. The following sections describe the tokenizer factory classes included in this release of Solr.
For user tips about Solr's tokenizers, see http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters.
== Standard Tokenizer == Standard Tokenizer
This tokenizer splits the text field into tokens, treating whitespace and punctuation as delimiters. Delimiter characters are discarded, with the following exceptions: This tokenizer splits the text field into tokens, treating whitespace and punctuation as delimiters. Delimiter characters are discarded, with the following exceptions:

2
solr/solr-ref-guide/src/update-request-processors.adoc
View File

@ -261,7 +261,7 @@ What follows are brief descriptions of the currently available update request pr
{solr-javadocs}/solr-core/org/apache/solr/update/processor/AtomicUpdateProcessorFactory.html[AtomicUpdateProcessorFactory]:: This processor will convert conventional field-value documents to atomic update documents. This processor can be used at runtime (without defining it in `solrconfig.xml`), see the section <<atomicupdateprocessorfactory>> below. {solr-javadocs}/solr-core/org/apache/solr/update/processor/AtomicUpdateProcessorFactory.html[AtomicUpdateProcessorFactory]:: This processor will convert conventional field-value documents to atomic update documents. This processor can be used at runtime (without defining it in `solrconfig.xml`), see the section <<atomicupdateprocessorfactory>> below.
{solr-javadocs}/solr-core/org/apache/solr/update/processor/ClassificationUpdateProcessorFactory.html[ClassificationUpdateProcessorFactory]:: This processor uses Lucene's classification module to provide simple document classification. See https://wiki.apache.org/solr/SolrClassification for more details on how to use this processor. {solr-javadocs}/solr-core/org/apache/solr/update/processor/ClassificationUpdateProcessorFactory.html[ClassificationUpdateProcessorFactory]:: This processor uses Lucene's classification module to provide simple document classification. See https://cwiki.apache.org/confluence/display/solr/SolrClassification for more details on how to use this processor.
{solr-javadocs}/solr-core/org/apache/solr/update/processor/CloneFieldUpdateProcessorFactory.html[CloneFieldUpdateProcessorFactory]:: Clones the values found in any matching _source_ field into the configured _dest_ field. {solr-javadocs}/solr-core/org/apache/solr/update/processor/CloneFieldUpdateProcessorFactory.html[CloneFieldUpdateProcessorFactory]:: Clones the values found in any matching _source_ field into the configured _dest_ field.

2
solr/solr-ref-guide/src/uploading-data-with-solr-cell-using-apache-tika.adoc
View File

@ -191,7 +191,7 @@ This parameter is valid only if `extractOnly` is set to true.
+ +
Example: `extractFormat=text` Example: `extractFormat=text`
+ +
Output: For an example output (in XML), see http://wiki.apache.org/solr/TikaExtractOnlyExampleOutput Output: For an example output (in XML), see https://cwiki.apache.org/confluence/display/solr/TikaExtractOnlyExampleOutput
`fmap._source_field_`:: `fmap._source_field_`::
Maps (moves) one field name to another. The `source_field` must be a field in incoming documents, and the value is the Solr field to map to. Maps (moves) one field name to another. The `source_field` must be a field in incoming documents, and the value is the Solr field to map to.

4
solr/solr-ref-guide/src/uploading-structured-data-store-data-with-the-data-import-handler.adoc
View File

@ -848,7 +848,9 @@ Transformers manipulate the fields in a document returned by an entity. A transf
Specific transformation rules are then added to the attributes of a `<field>` element, as shown in the examples below. The transformers are applied in the order in which they are specified in the transformer attribute. Specific transformation rules are then added to the attributes of a `<field>` element, as shown in the examples below. The transformers are applied in the order in which they are specified in the transformer attribute.
The DataImportHandler contains several built-in transformers. You can also write your own custom transformers, as described in the http://wiki.apache.org/solr/DIHCustomTransformer[DIHCustomTransformer] section of the Solr Wiki. The ScriptTransformer (described below) offers an alternative method for writing your own transformers. The DataImportHandler contains several built-in transformers.
You can also write your own custom transformers if necessary.
The ScriptTransformer described below offers an alternative method for writing your own transformers.
=== ClobTransformer === ClobTransformer

3
solr/solr-ref-guide/src/velocity-response-writer.adoc
View File

@ -100,7 +100,7 @@ Resource bundles can be added by providing a JAR file visible by the SolrResourc
|=== |===
|Context Reference |Description |Context Reference |Description
|`request` |{solr-javadocs}solr-core/org/apache/solr/request/SolrQueryRequest.html[SolrQueryRequest] javadocs |`request` |{solr-javadocs}solr-core/org/apache/solr/request/SolrQueryRequest.html[SolrQueryRequest] javadocs
|`response` |{solr-javadocs}solr-core/org/apache/solr/response/SolrQueryResponse.html[QueryResponse] most of the time, but in some cases where QueryResponse doesn't like the request handler's output (https://wiki.apache.org/solr/AnalysisRequestHandler[AnalysisRequestHandler], for example, causes a ClassCastException parsing "response"), the response will be a SolrResponseBase object. |`response` |{solr-javadocs}solr-core/org/apache/solr/response/SolrQueryResponse.html[QueryResponse] most of the time, but in some cases where QueryResponse doesn't like the request handler's output (https://cwiki.apache.org/confluence/display/solr/AnalysisRequestHandler[AnalysisRequestHandler], for example, causes a ClassCastException parsing "response"), the response will be a SolrResponseBase object.
|`esc` |A Velocity http://velocity.apache.org/tools/{ivy-velocity-tools-version}/tools-summary.html#EscapeTool[EscapeTool] instance |`esc` |A Velocity http://velocity.apache.org/tools/{ivy-velocity-tools-version}/tools-summary.html#EscapeTool[EscapeTool] instance
|`date` |A Velocity http://velocity.apache.org/tools/{ivy-velocity-tools-version}/tools-summary.html#ComparisonDateTool[ComparisonDateTool] instance |`date` |A Velocity http://velocity.apache.org/tools/{ivy-velocity-tools-version}/tools-summary.html#ComparisonDateTool[ComparisonDateTool] instance
|`math` |A Velocity http://velocity.apache.org/tools/{ivy-velocity-tools-version}/tools-summary.html#MathTool[MathTool] instance |`math` |A Velocity http://velocity.apache.org/tools/{ivy-velocity-tools-version}/tools-summary.html#MathTool[MathTool] instance
@ -120,4 +120,3 @@ Resource bundles can be added by providing a JAR file visible by the SolrResourc
To see results in an HTML user interface on your own collection, try http://localhost:8983/solr/<my collection>/select?q=*:*&wt=velocity&v.template=browse&v.layout=layout To see results in an HTML user interface on your own collection, try http://localhost:8983/solr/<my collection>/select?q=*:*&wt=velocity&v.template=browse&v.layout=layout
Or try `/browse` in the examples techproducts or example/files. Or try `/browse` in the examples techproducts or example/files.

2
solr/solr-ref-guide/src/working-with-dates.adoc
View File

@ -170,4 +170,4 @@ fq={!field f=dateRange op=Contains}[2013 TO 2018]
Unlike most local parameters, `op` is actually _not_ defined by any query parser (`field`), it is defined by the field type, in this case `DateRangeField`. In the above example, it would find documents with indexed ranges that _contain_ (or equals) the range 2013 thru 2018. Multi-valued overlapping indexed ranges in a document are effectively coalesced. Unlike most local parameters, `op` is actually _not_ defined by any query parser (`field`), it is defined by the field type, in this case `DateRangeField`. In the above example, it would find documents with indexed ranges that _contain_ (or equals) the range 2013 thru 2018. Multi-valued overlapping indexed ranges in a document are effectively coalesced.
For a DateRangeField example use-case, see http://wiki.apache.org/solr/DateRangeField[see Solr's community wiki]. For a DateRangeField example use-case, see https://cwiki.apache.org/confluence/display/solr/DateRangeField[see Solr's community wiki].