This may be related to SOLR-1742 and/or SOLR-1743. I have a minimal schema file, 4 fields and one copyfield. If UniqueKey isn't specified in the schema file, going to the admin page produces a "missing core name in path" error. I can't seem to add documents via Posting either.
This is with a SOLR downloaded and compiled this morning (Sunday, 14-Feb). Does anyone have a clue about this or am I seeing things? Same thing happens with the 1.4 release. The *only* difference between success and failure is removing (or not) <UniqueKey>. Yet we state that the unique key isn't required at http://wiki.apache.org/solr/SchemaXml#The_Unique_Key_Field. And specifying required="false" doesn't seem to change things. To try to get this to a minimal set of things to look at, I deleted my index directory completely and saw the above, before indexing anything. If I leave UniqueKey in, the admin page shows up fine. Even with required="false" (both for field and UniqueKey), indexing a document via post fails with "...Status 400 - Document is missing uniqueKey field id</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b>" Running under Tomcat on a Mac if it matters, Java 1.6 Erick Here's the (I believe) relevant portion of my schema file... <fields> <field name="title" type="text" indexed="true" stored="true" required="true" /> <field name="body" type="text" indexed="true" stored="true" required="true" /> <field name="author" type="text" indexed="true" stored="true" required="true" /> <field name="title_sort" type="alphaOnlySort" indexed="true" stored="true" required="true" /> <field name="id" type="string" indexed="true" stored="true" required="false"/> </fields> <uniqueKey required="false">id</uniqueKey> <!-- field for the QueryParser to use when an explicit fieldname is absent --> <defaultSearchField>body</defaultSearchField> <!-- SolrQueryParser configuration: defaultOperator="AND|OR" --> <solrQueryParser defaultOperator="OR"/> <copyField source="title" dest="title_sort"/>
