It seems that you are using the bbyopen data. If have made up your mind on using the JSON data then simply store it in ElasticSearch instead of Solr as they do take any valid JSON structure. Otherwise, you can download the xml archive from bbyopen and prepare a schema:
Here are some generic instructions to familiarize you with building schema given arbitrary data, it should help speed things up, they don't apply directly to bbyopen data though: http://pulkitsinghal.blogspot.com/2011/10/import-dynamic-fields-from-xml-into.html http://pulkitsinghal.blogspot.com/2011/09/import-data-from-amazon-rss-feeds-into.html Keep in mind, ES also does you a favor by building the right schema dynamically on the fly as you feed it the JSON data. So it is much easier to work with. On Fri, Mar 16, 2012 at 1:26 PM, Erick Erickson <erickerick...@gmail.com>wrote: > bq: Shouldn't it be able to take any valid JSON structure? > > No, that was never the intent. The intent here was just to provide > a JSON-compatible format for indexing data for those who > don't like/want to use XML or SolrJ or.... Solr doesn't index arbitrary > XML either. And I have a hard time imagining what the > schema.xml file would look like when trying to map > arbitrary JSON (or XML or....) into fields. > > Best > Erick > > On Fri, Mar 16, 2012 at 12:54 PM, Chambeda <chamb...@gmail.com> wrote: > > Ok, so my issue is that it must be a flat structure. Why isn't the JSON > > parser able to deconstruct the object into a flatter structure for > indexing? > > Shouldn't it be able to take any valid JSON structure? > > > > -- > > View this message in context: > http://lucene.472066.n3.nabble.com/Error-while-trying-to-load-JSON-tp3832518p3832611.html > > Sent from the Solr - User mailing list archive at Nabble.com. >
