Thank you, Thomas! Changing the required to false allowed the document to be indexed. I did not gleam this information from the SOLR documentation regarding nested documents. Do you know of any good sources for educational material on this subject? I cannot change the payloads that I am working with unfortunately. They make heavy use of deeply nested json object. Thank you again for your assistance, it is most appreciated! ________________________________ From: Thomas Corthals <tho...@klascement.net> Sent: Thursday, October 27, 2022 1:34 AM To: Matthew Castrigno <castr...@slhs.org> Cc: users@solr.apache.org <users@solr.apache.org> Subject: Re: I cannot get nested objects to index - with image links
Hi Matthew All the fields in your schema are required="true". This means they are required for all documents, whether parents or children (or standalone). "Required" fields (from a business logic perspective) on parents ZjQcmQRYFpfptBannerStart This Message Is From an Untrusted Sender You have not previously corresponded with this sender. ZjQcmQRYFpfptBannerEnd Hi Matthew All the fields in your schema are required="true". This means they are required for all documents, whether parents or children (or standalone). "Required" fields (from a business logic perspective) on parents and children will usually be different and that can't be enforced in a Solr schema. The only fields that can be required="true" are the ones that are required for all types of documents. The uniqueKeyField is definitely one of them. For all other fields, it might make more sense to handle this constraint in your application. Thomas Op do 27 okt. 2022 om 01:08 schreef Matthew Castrigno <castr...@slhs.org<mailto:castr...@slhs.org>>: Thank you so much for your response, Thomas, I do appreciate it. I made the changes, but I am getting a different error now. Did I not interpret your instructions correctly? https://i.postimg.cc/SNM4t7vs/updated-schema.png [i.postimg.cc]<https://urldefense.com/v3/__https://i.postimg.cc/SNM4t7vs/updated-schema.png__;!!FkC3_z_N!JJcOTo8MLWYS72yOLdGmPbY8vOwX_B_w1HO2eCNy2NK_4nSWBTu3eKknYiA8rgpJ4E66YWvLPJeAa1Gl$> https://i.postimg.cc/RZtcF8bB/Screenshot-2022-10-26-170222.png [i.postimg.cc]<https://urldefense.com/v3/__https://i.postimg.cc/RZtcF8bB/Screenshot-2022-10-26-170222.png__;!!FkC3_z_N!JJcOTo8MLWYS72yOLdGmPbY8vOwX_B_w1HO2eCNy2NK_4nSWBTu3eKknYiA8rgpJ4E66YWvLPNYoRUGC$> ________________________________ From: Thomas Corthals <tho...@klascement.net<mailto:tho...@klascement.net>> Sent: Tuesday, October 25, 2022 1:28 AM To: users@solr.apache.org<mailto:users@solr.apache.org> <users@solr.apache.org<mailto:users@solr.apache.org>> Subject: Re: I cannot get nested objects to index - with image links Hi Matthew The (pseudo-)field in which you want to put the nested documents ("content" in your example) should not be added to the schema. The actual fields of the nested document (id, stuff1, stuff2) need to match an explicit field definition ZjQcmQRYFpfptBannerStart This Message Is From an Untrusted Sender You have not previously corresponded with this sender. ZjQcmQRYFpfptBannerEnd Hi Matthew The (pseudo-)field in which you want to put the nested documents ("content" in your example) should not be added to the schema. The actual fields of the nested document (id, stuff1, stuff2) need to match an explicit field definition or a dynamicField definition in your schema though. Thomas Op ma 24 okt. 2022 om 23:48 schreef Matthew Castrigno <castr...@slhs.org<mailto:castr...@slhs.org>>: > Hello Community, Thank you for taking the time to read my message. > > I am attempting to index (update) a document with a nested object. > > In reading the documentation is seems to state that the fields of the > nested object do not need to be and should not be added > > to schema.xml. I am getting error that the field of the nested object is > undefined, and I am not sure what I am doing wrong. > > Any insights appreciated. Thank you > > https://urldefense.com/v3/__https://i.postimg.cc/25GtB1Mc/update.png__;!!FkC3_z_N!MH9mbztbPvc05Og3x_fcnapmPzux7fhqgdChsAIR0bqiTiV_-BVnIdI8Z---HIWeD5TLbiwytoGIDSsB$ > > https://urldefense.com/v3/__https://i.postimg.cc/SKk5s6TY/schema.png__;!!FkC3_z_N!MH9mbztbPvc05Og3x_fcnapmPzux7fhqgdChsAIR0bqiTiV_-BVnIdI8Z---HIWeD5TLbiwytlHh85s3$ > > ---------------------------------------------------------------------- > "This message is intended for the use of the person or entity to which it > is addressed and may contain information that is confidential or > privileged, the disclosure of which is governed by applicable law. If the > reader of this message is not the intended recipient, you are hereby > notified that any dissemination, distribution, or copying of this > information is strictly prohibited. If you have received this message by > error, please notify us immediately and destroy the related message." > ________________________________ "This message is intended for the use of the person or entity to which it is addressed and may contain information that is confidential or privileged, the disclosure of which is governed by applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is strictly prohibited. If you have received this message by error, please notify us immediately and destroy the related message." ---------------------------------------------------------------------- "This message is intended for the use of the person or entity to which it is addressed and may contain information that is confidential or privileged, the disclosure of which is governed by applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is strictly prohibited. If you have received this message by error, please notify us immediately and destroy the related message."
