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

Ref Guide: typos and small edits

This commit is contained in:
Cassandra Targett 2018-01-11 08:39:57 -06:00
parent 4dac5aad1a
commit 60c6890ff0
3 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
solr/solr-ref-guide/src/distributed-requests.adoc
View File

@ -61,7 +61,7 @@ Or you can specify a list of replicas to choose from for a single shard (for loa
http://localhost:8983/solr/gettingstarted/select?q=*:*&shards=localhost:7574/solr/gettingstarted|localhost:7500/solr/gettingstarted
----
And of course, you can specify a list of shards (seperated by commas) each defined by a list of replicas (seperated by pipes). In this example, 2 shards are queried, the first being a random replica from shard1, the second being a random replica from the explicit pipe delimited list:
And of course, you can specify a list of shards (separated by commas) each defined by a list of replicas (seperated by pipes). In this example, 2 shards are queried, the first being a random replica from shard1, the second being a random replica from the explicit pipe delimited list:
[source,text]
----

2
solr/solr-ref-guide/src/format-of-solr-xml.adoc
View File

@ -155,7 +155,7 @@ Custom shard handlers can be defined in `solr.xml` if you wish to create a custo
<shardHandlerFactory name="ShardHandlerFactory" class="qualified.class.name">
----
Since this is a custom shard handler, sub-elements are specific to the implementation. The default and only shard handler provided by Solr is the HttpShardHandlerFactory in which case, the following sub-elements can be specified:
Since this is a custom shard handler, sub-elements are specific to the implementation. The default and only shard handler provided by Solr is the `HttpShardHandlerFactory` in which case, the following sub-elements can be specified:
`socketTimeout`::
The read timeout for intra-cluster query and administrative requests. The default is the same as the `distribUpdateSoTimeout` specified in the `<solrcloud>` section.

12
solr/solr-ref-guide/src/suggester.adoc
View File

@ -194,22 +194,22 @@ An extension of the `AnalyzingInfixSuggester` which provides additional function
This implementation uses the following additional properties:
`blenderType`::
Used to calculate weight coefficient using the position of the first matching word. Can be one of:
Used to calculate weight coefficient using the position of the first matching word. Available options are:
`position_linear`:::
`weightFieldValue*(1 - 0.10*position)`: Matches to the start will be given a higher score. This is the default.
`weightFieldValue * (1 - 0.10*position)`: Matches to the start will be given a higher score. This is the default.
`position_reciprocal`:::
`weightFieldValue/(1+position)`: Matches to the end will be given a higher score.
`weightFieldValue / (1 + position)`: Matches to the end will be given a higher score.
`exponent`::::
An optional configuration variable for the position_reciprocal blenderType used to control how fast the score will increase or decrease. Default `2.0`.
An optional configuration variable for `position_reciprocal` to control how fast the score will increase or decrease. Default `2.0`.
`numFactor`::
The factor to multiply the number of searched elements from which results will be pruned. Default is `10`.
`indexPath`::
When using `BlendedInfixSuggester` you can provide your own path where the index will get built. The default directory name is `blendedInfixSuggesterIndexDir` and will be created in your collections data directory.
When using `BlendedInfixSuggester` you can provide your own path where the index will get built. The default directory name is `blendedInfixSuggesterIndexDir` and will be created in your collection's data directory.
`minPrefixChars`::
Minimum number of leading characters before PrefixQuery is used (the default is `4`). Prefixes shorter than this are indexed as character ngrams (increasing index size but making lookups faster).
Minimum number of leading characters before PrefixQuery is used (the default is `4`). Prefixes shorter than this are indexed as character ngrams, which increases index size but makes lookups faster.
This implementation supports <<Context Filtering>>.