<!-- 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". --> <field name="id" type="string" indexed ="true" stored="true" required="true" multiValued="false" />
and further on in the file... <!-- Field to use to determine and enforce document uniqueness. Unless this field is marked with required="false", it will be a required field --> < uniqueKey>id</uniqueKey> On Tue, Jul 26, 2016 at 2:17 PM, John Bickerstaff <j...@johnbickerstaff.com> wrote: > I don't see a managed schema file. As far as I understand it, id is set > as a "uniqueKey" in the schema.xml file... > > On Tue, Jul 26, 2016 at 2:11 PM, Michael Joyner <mich...@newsrx.com> > wrote: > >> ok, I think I need to do a manual edit on the managed-schema file but I >> get "NoNode" for /managed-schema when trying to use the zkcli.sh file? >> >> >> How can I get to this file and edit it? >> >> >> On 07/26/2016 03:05 PM, Alexandre Drouin wrote: >> >>> Hello, >>> >>> You may have a uniqueKey that points to a field that do not exists >>> anymore. You can try adding an "id" field using Solr's UI or the schema >>> API since you are using the managed-schema. >>> >>> >>> Alexandre Drouin >>> >>> -----Original Message----- >>> From: Michael Joyner [mailto:mich...@newsrx.com] >>> Sent: July 26, 2016 2:34 PM >>> To: solr-user@lucene.apache.org >>> Subject: Can't load schema managed-schema: unknown field 'id' >>> >>> |Help!| >>> >>> | >>> | >>> >>> |What is the best way to recover from: | >>> >>> Can't load schema managed-schema: unknown field 'id' >>> |I was managing the schema on a test collection, fat fingered it, but now >>> I find out the schema ops seem to altering all collections on the core? >>> SolrCloud 5.5.1 ||| >>> >>> | >>> -Mike||| >>> >> >> >
