svn commit: r1661427 - in /lucene/dev/trunk/solr/server/solr/configsets: basic_configs/conf/schema.xml sample_techproducts_configs/conf/schema.xml

[er...@apache.org]

Author: erick
Date: Sat Feb 21 18:51:34 2015
New Revision: 1661427

URL: http://svn.apache.org/r1661427
Log:
Add a comment to the schema.xml file(s) warning against applying analysis chains to the <uniqueKey> field.

Modified:
    lucene/dev/trunk/solr/server/solr/configsets/basic_configs/conf/schema.xml
    lucene/dev/trunk/solr/server/solr/configsets/sample_techproducts_configs/conf/schema.xml

Modified: lucene/dev/trunk/solr/server/solr/configsets/basic_configs/conf/schema.xml
URL: http://svn.apache.org/viewvc/lucene/dev/trunk/solr/server/solr/configsets/basic_configs/conf/schema.xml?rev=1661427&r1=1661426&r2=1661427&view=diff
==============================================================================
--- lucene/dev/trunk/solr/server/solr/configsets/basic_configs/conf/schema.xml (original)
+++ lucene/dev/trunk/solr/server/solr/configsets/basic_configs/conf/schema.xml Sat Feb 21 18:51:34 2015
@@ -103,6 +103,11 @@
    <!-- 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 
      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" /> 
 

Modified: lucene/dev/trunk/solr/server/solr/configsets/sample_techproducts_configs/conf/schema.xml
URL: http://svn.apache.org/viewvc/lucene/dev/trunk/solr/server/solr/configsets/sample_techproducts_configs/conf/schema.xml?rev=1661427&r1=1661426&r2=1661427&view=diff
==============================================================================
--- lucene/dev/trunk/solr/server/solr/configsets/sample_techproducts_configs/conf/schema.xml (original)
+++ lucene/dev/trunk/solr/server/solr/configsets/sample_techproducts_configs/conf/schema.xml Sat Feb 21 18:51:34 2015
@@ -119,6 +119,11 @@
    <!-- 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 
      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" />