mirror of https://github.com/apache/lucene.git
doc - format upgrading section for 80 cols
git-svn-id: https://svn.apache.org/repos/asf/lucene/solr/trunk@823692 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
d528c57d50
commit
362ad79804
13
CHANGES.txt
13
CHANGES.txt
|
@ -30,12 +30,13 @@ There is a new default faceting algorithm for multiVaued fields that should be
|
||||||
faster for most cases. One can revert to the previous algorithm (which has
|
faster for most cases. One can revert to the previous algorithm (which has
|
||||||
also been improved somewhat) by adding facet.method=enum to the request.
|
also been improved somewhat) by adding facet.method=enum to the request.
|
||||||
|
|
||||||
New users of Solr 1.4 will have omitTermFreqAndPositions enabled for non-text indexed fields by
|
New users of Solr 1.4 will have omitTermFreqAndPositions enabled for non-text
|
||||||
default, which avoids indexing term frequency, positions, and payloads, making
|
indexed fields by default, which avoids indexing term frequency, positions, and
|
||||||
the index smaller and faster. If you are upgrading from an earlier Solr
|
payloads, making the index smaller and faster. If you are upgrading from an
|
||||||
release and want to enable omitTermFreqAndPositions by default, change the schema version from
|
earlier Solr release and want to enable omitTermFreqAndPositions by default,
|
||||||
1.1 to 1.2 in schema.xml. Remove any existing index and restart Solr to ensure that omitTermFreqAndPositions
|
change the schema version from 1.1 to 1.2 in schema.xml. Remove any existing
|
||||||
completely takes affect.
|
index and restart Solr to ensure that omitTermFreqAndPositions completely takes
|
||||||
|
affect.
|
||||||
|
|
||||||
The default QParserPlugin used by the QueryComponent for parsing the "q" param
|
The default QParserPlugin used by the QueryComponent for parsing the "q" param
|
||||||
has been changed, to remove support for the deprecated use of ";" as a separator
|
has been changed, to remove support for the deprecated use of ";" as a separator
|
||||||
|
|
Loading…
Reference in New Issue