mirror of https://github.com/apache/lucene.git
SOLR-11078: Add note about the trade-off between Point and Trie fields.
This commit is contained in:
parent
5b4efc5a41
commit
d84c92ed11
|
@ -662,6 +662,9 @@ Upgrading from Solr 6.x
|
|||
----------------------
|
||||
|
||||
* All Trie* numeric and date field types have been deprecated in favor of *Point field types.
|
||||
Point field types are better at range queries (speed, memory, disk), however simple field:value queries underperform
|
||||
relative to Trie. Either accept this, or continue to use Trie fields.
|
||||
This shortcoming may be addressed in a future release.
|
||||
|
||||
* The default response type is now JSON ("wt=json") instead of XML, and line indentation is now on by default
|
||||
("indent=on"). If you expect the responses to your queries to be returned in the previous format (XML
|
||||
|
|
|
@ -87,3 +87,8 @@ Configuration and usage of PreAnalyzedField is documented in the section <<work
|
|||
|
||||
*Note*: configuring a UUIDField instance with a default value of `NEW` is not advisable for most users when using SolrCloud (and not possible if the UUID value is configured as the unique key field) since the result will be that each replica of each document will get a unique UUID value. Using UUIDUpdateProcessorFactory to generate UUID values when documents are added is recommended instead.
|
||||
|===
|
||||
|
||||
NOTE: All Trie* numeric and date field types have been deprecated in favor of *Point field types.
|
||||
Point field types are better at range queries (speed, memory, disk), however simple field:value queries underperform
|
||||
relative to Trie. Either accept this, or continue to use Trie fields.
|
||||
This shortcoming may be addressed in a future release.
|
Loading…
Reference in New Issue