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

Add a comment to the schema.xml file(s) warning against applying analysis chains to the <uniqueKey> field. 

git-svn-id: https://svn.apache.org/repos/asf/lucene/dev/trunk@1661427 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Erick Erickson 2015-02-21 18:51:34 +00:00
parent 163c0bc0b7
commit 6c8dc4e115
2 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
solr/server/solr/configsets/basic_configs/conf/schema.xml
View File

@ -103,6 +103,11 @@
<!-- Only remove the "id" field if you have a very good reason to. While not strictly <!-- Only remove the "id" field if you have a very good reason to. While not strictly
required, it is highly recommended. A <uniqueKey> is present in almost all Solr required, it is highly recommended. A <uniqueKey> is present in almost all Solr
installations. See the <uniqueKey> declaration below where <uniqueKey> is set to "id". installations. See the <uniqueKey> declaration below where <uniqueKey> is set to "id".
Do NOT change the type and apply index-time analysis to the <uniqueKey> as it will likely
make routing in SolrCloud and document replacement in general fail. Limited _query_ time
analysis is possible as long as the indexing process is guaranteed to index the term
in a compatible way. Any analysis applied to the <uniqueKey> should _not_ produce multiple
tokens
--> -->
<field name="id" type="string" indexed="true" stored="true" required="true" multiValued="false" /> <field name="id" type="string" indexed="true" stored="true" required="true" multiValued="false" />

5
solr/server/solr/configsets/sample_techproducts_configs/conf/schema.xml
View File

@ -119,6 +119,11 @@
<!-- Only remove the "id" field if you have a very good reason to. While not strictly <!-- Only remove the "id" field if you have a very good reason to. While not strictly
required, it is highly recommended. A <uniqueKey> is present in almost all Solr required, it is highly recommended. A <uniqueKey> is present in almost all Solr
installations. See the <uniqueKey> declaration below where <uniqueKey> is set to "id". installations. See the <uniqueKey> declaration below where <uniqueKey> is set to "id".
Do NOT change the type and apply index-time analysis to the <uniqueKey> as it will likely
make routing in SolrCloud and document replacement in general fail. Limited _query_ time
analysis is possible as long as the indexing process is guaranteed to index the term
in a compatible way. Any analysis applied to the <uniqueKey> should _not_ produce multiple
tokens
--> -->
<field name="id" type="string" indexed="true" stored="true" required="true" multiValued="false" /> <field name="id" type="string" indexed="true" stored="true" required="true" multiValued="false" />