Hi James Yonick has a great blog explaining that, but I am on the bus so I do not have a link for you.
Yes, you can use nesting, and there are good reasons for doing so, but you will find it much easier to use flat fields. YMMV Cheers -- Rick On March 8, 2018 5:22:13 PM EST, "kasinger, james" <james.kasin...@nordstrom.com> wrote: >Not quite. This will index the nested json into a flattened >representation of the data, in multiple documents. We expect the >resulting document to contain all the same nested fields as the json >had. It should be identical. > >Thanks for your response, >Jams > >On 3/8/18, 1:26 PM, "Mikhail Khludnev" <m...@apache.org> wrote: > > Will >https://lucene.apache.org/solr/guide/7_1/transforming-and-indexing-custom-json.html > work > for you? > > On Thu, Mar 8, 2018 at 8:17 PM, kasinger, james < > james.kasin...@nordstrom.com> wrote: > > > Hi folks, >> Has anyone had success indexing nested json into solr? I know that >solr >> prefers a flattened representation of the data, but I’m exploring >potential > > solutions or workarounds for achieving this. Thanks in advance. > > >> For instance I’m indexing this “document” and expect it to be >presented in > > solr in the same way. > > > > { > > "rolledupcolors": [ > > { > > "Name": "BURGUNDY", > > "ManiImageUrl":"1/_102069221.jpg", > > "AltImageUrl":"3/_102067603.jpg", > > "RGB":"", > > "ColorFamily":"Red,Purple", > > "SwatchImageUrl":"2/_102067602.jpg" > > }, > > { > > "Name": "CHARCOAL", > > ........ > > } > > ] > > } > > > > James > > > > > > > > > -- > Sincerely yours > Mikhail Khludnev > -- Sorry for being brief. Alternate email is rickleir at yahoo dot com
