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

example: update to reflect new sortMissingLast 

git-svn-id: https://svn.apache.org/repos/asf/lucene/dev/trunk@1026822 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Yonik Seeley 2010-10-24 15:23:42 +00:00
parent 3fc24d327e
commit 5150971448
1 changed files with 4 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
solr/example/solr/conf/schema.xml
View File

@ -73,9 +73,8 @@
<!--Binary data type. The data should be sent/retrieved in as Base64 encoded Strings --> <!--Binary data type. The data should be sent/retrieved in as Base64 encoded Strings -->
<fieldtype name="binary" class="solr.BinaryField"/> <fieldtype name="binary" class="solr.BinaryField"/>
<!-- The optional sortMissingLast and sortMissingFirst attributes are <!-- sortMissingLast and sortMissingFirst attributes are optional attributes
currently supported on types that are sorted internally as strings. that control how fields are sorted when values are missing.
This includes "string","boolean","sint","slong","sfloat","sdouble","pdate"
- If sortMissingLast="true", then a sort on this field will cause documents - If sortMissingLast="true", then a sort on this field will cause documents
without the field to come after documents with the field, without the field to come after documents with the field,
regardless of the requested sort order (asc or desc). regardless of the requested sort order (asc or desc).
@ -140,11 +139,10 @@
<!-- <!--
Note: Note:
These should only be used for compatibility with existing indexes (created with older Solr versions) These should only be used for compatibility with existing indexes (created with lucene or older Solr versions).
or if "sortMissingFirst" or "sortMissingLast" functionality is needed. Use Trie based fields instead.
Plain numeric field types that store and index the text Plain numeric field types that store and index the text
value verbatim (and hence don't support range queries, since the value verbatim (and hence don't correctly support range queries, since the
lexicographic ordering isn't equal to the numeric ordering) lexicographic ordering isn't equal to the numeric ordering)
--> -->
<fieldType name="pint" class="solr.IntField" omitNorms="true"/> <fieldType name="pint" class="solr.IntField" omitNorms="true"/>
@ -153,23 +151,6 @@
<fieldType name="pdouble" class="solr.DoubleField" omitNorms="true"/> <fieldType name="pdouble" class="solr.DoubleField" omitNorms="true"/>
<fieldType name="pdate" class="solr.DateField" sortMissingLast="true" omitNorms="true"/> <fieldType name="pdate" class="solr.DateField" sortMissingLast="true" omitNorms="true"/>
<!--
Note:
These should only be used for compatibility with existing indexes (created with older Solr versions)
or if "sortMissingFirst" or "sortMissingLast" functionality is needed. Use Trie based fields instead.
Numeric field types that manipulate the value into
a string value that isn't human-readable in its internal form,
but with a lexicographic ordering the same as the numeric ordering,
so that range queries work correctly.
-->
<fieldType name="sint" class="solr.SortableIntField" sortMissingLast="true" omitNorms="true"/>
<fieldType name="slong" class="solr.SortableLongField" sortMissingLast="true" omitNorms="true"/>
<fieldType name="sfloat" class="solr.SortableFloatField" sortMissingLast="true" omitNorms="true"/>
<fieldType name="sdouble" class="solr.SortableDoubleField" sortMissingLast="true" omitNorms="true"/>
<!-- The "RandomSortField" is not used to store or search any <!-- The "RandomSortField" is not used to store or search any
data. You can declare fields of this type it in your schema data. You can declare fields of this type it in your schema
to generate pseudo-random orderings of your docs for sorting to generate pseudo-random orderings of your docs for sorting