Hi Erick As per the documentation - > https://urldefense.proofpoint.com/v2/url?u=https-3A__lucene.apache.org > _solr_guide_7-5F5_updating-2Dparts-2Dof-2Ddocuments.html-23field-2Dsto > rage&d=DwIDaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=HEBHcZdI > eDHAvl73r3r2wMPqU2fuBMQEqkrJDiOkgU0&m=E0eYGosr2K2uq4yr-Kk3r1d49jU0cFLh > akbRohIP0rQ&s=o3x6BbYYdEkVFyvQKF3ZIZlwV5iBh3J3lsskRzt--S8&e=
For atomic updates to work either Stored or docValues is to be true. Current configuration satisfies this condition. " The core functionality of atomically updating a document requires that all fields in your schema must be configured as stored (stored="true") or docValues (docValues="true")" Anyways will give a try by setting stored =true and also setting usedocValuesAsStored="true" will update you soon. Thanks Rajeswari -----Original Message----- From: Erick Erickson [mailto:erickerick...@gmail.com] Sent: Wednesday, November 21, 2018 10:34 AM To: solr-user <solr-user@lucene.apache.org> Subject: Re: Error:Missing Required Fields for Atomic Updates bq. While creating a document , I have provide the required information to field "category". But you did not store it, you have stored="false" for that field. Atomic updates require that all source fields are stored. What happens under the covers is that the stored data is read from the doc, your update is overlaid and the doc is re-indexed. And since category is not stored, it's not present in the new index and the update fails. That's just the way atomic updates work. That said, if you _do_ store the cat field and still have this problem a JIRA would be in order. Frankly I do not know if setting docValues="true" and usedocValuesAsStored="true" will work or not, have you tried? Best, Erick On Tue, Nov 20, 2018 at 8:06 PM Rajeswari Kolluri <rajeswari.koll...@oracle.com> wrote: > > Hi Shawn, > > Schema version is 1.6 and Solr version is 7.5. > > While creating a document , I have provide the required information to field > " category". > > Now, I would like to update document for other set of fields using Atomic > Update but not category field. > > While performing atomic update ,exception caught with "Missing required field > on category". > > > Thanks > Rajeswari > > -----Original Message----- > From: Shawn Heisey [mailto:apa...@elyograg.org] > Sent: Tuesday, November 20, 2018 8:38 PM > To: solr-user@lucene.apache.org > Subject: Re: Error:Missing Required Fields for Atomic Updates > > On 11/19/2018 9:19 PM, Rajeswari Kolluri wrote: > > Below is part of schema , entityid is my unique id field. Getting > > exception missing required field for "category" during atomic updates. > <snip> > > <field name="category" type="string" indexed="true" > > stored="false" required="true" docValues="true" /> > > Your category field is not stored. And it's required. It does have > docValues, but unless your Solr version and schema version are new enough, > this definition will make the field unsuitable for atomic updates. > > What is your Solr version, and what version do you have declared in > your schema? (newest schema version that I know about is 1.6) > > This is the information about what's needed for Atomic Updates to work: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__lucene.apache.org > _solr_guide_7-5F5_updating-2Dparts-2Dof-2Ddocuments.html-23field-2Dsto > rage&d=DwIDaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=HEBHcZdI > eDHAvl73r3r2wMPqU2fuBMQEqkrJDiOkgU0&m=E0eYGosr2K2uq4yr-Kk3r1d49jU0cFLh > akbRohIP0rQ&s=o3x6BbYYdEkVFyvQKF3ZIZlwV5iBh3J3lsskRzt--S8&e= > > That documentation is not as specific as it needs to be when it says that the > field can have docValues enabled to meet the requirements. You must also > have useDocValuesAsStored enabled. This is enabled by default if your schema > version is 1.6 or later ... which is the schema version that examples are set > to in the later releases of Solr. But if your schema was designed for an > earlier version of Solr, its version probably may be something earlier than > 1.6. > > The minimum Solr version required to be able to use docValues as stored is > 5.5.0. If you have a Solr version before 5.5.0, docValues will not work for > atomic updates at all. > > Thanks, > Shawn >
